
🔴 MicrosoftOpenApiYamlReader, Uncontrolled Resource Consumption, #CVE-2026-72923 (Critical) -DC-Oct2026-3218 https://dailycve.com/microsoftopenapiyamlreader-uncontrolled-resource-consumption-cve-2026-72923-critical-dc-oct2026-3218/
Signal is active with 1 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD description
The OpenAPI.NET SDK contains a useful object model for OpenAPI documents in .NET along with common serializers to extract raw OpenAPI JSON and YAML documents from the model. In Microsoft.OpenApi.Readers versions before 1.6.30 and Microsoft.OpenApi.YamlReader from 2.0.0-preview.11 through 2.11.0 and 3.0.0 through 3.9.0, parsing a YAML OpenAPI document with nested anchors and aliases can consume uncontrolled memory. SharpYaml represents aliases as shared nodes in a small directed acyclic graph, but conversion to independent OpenAPI or System.Text.Json.Nodes.JsonNode trees duplicates every aliased path; without a node-count or nesting-depth limit, N nested anchors referenced k times can require k^N materialized nodes and terminate the process through an out-of-memory condition. The fixed readers bound materialization to 5,000,000 nodes and a nesting depth of 64 by default and report an OpenApiDiagnostic error when a limit is exceeded. This vulnerability is fixed in Microsoft.OpenApi.Readers 1.6.30 and Microsoft.OpenApi.YamlReader 2.12.0 and 3.10.0.
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
NONE
Momentum
NONE

🔴 MicrosoftOpenApiYamlReader, Uncontrolled Resource Consumption, #CVE-2026-72923 (Critical) -DC-Oct2026-3218 https://dailycve.com/microsoftopenapiyamlreader-uncontrolled-resource-consumption-cve-2026-72923-critical-dc-oct2026-3218/