CVE-2026-72923
- Source
- https://cve.org/CVERecord?id=CVE-2026-72923
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-72923.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-72923
- Aliases
-
- GHSA-7pxr-59rr-hqj2
- Published
- 2026-09-08T17:12:20Z
- Modified
- 2026-09-12T03:30:52Z
- Severity
-
- 7.5 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
- Summary
- Microsoft.OpenApi.YamlReader/Readers vulnerable to denial of service via YAML alias expansion
- Details
-
In Microsoft.OpenApi.YamlReader from 2.0.0-preview.11 until 2.12.0 and from 3.0.0 until 3.10.0, and in Microsoft.OpenApi.Readers prior to 1.6.30, a small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption when parsed through the public YAML reader APIs. YAML is parsed through SharpYaml, which represents aliases as shared nodes in a directed acyclic graph, so the parsed YAML graph stays small, but converting that graph to System.Text.Json.Nodes.JsonNode requires every alias to be materialized as an independent node because a JsonNode cannot be attached to multiple parents. Without a bound on that conversion work, a document with N nested anchors each referenced k times can require k^N materialized JSON nodes, leading to excessive memory allocation and process termination through out-of-memory conditions, a billion laughs style denial of service. The patched versions bound the YAML-to-JSON conversion by node count and nesting depth and report an OpenApiDiagnostic error instead of expanding without limit. This vulnerability is fixed in Microsoft.OpenApi.YamlReader 2.12.0 and 3.10.0, and Microsoft.OpenApi.Readers 1.6.30.
- Database specific
{ "cna_assigner": "GitHub_M", "cwe_ids": [ "CWE-400" ], "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/72xxx/CVE-2026-72923.json" }- References
Affected packages
Git / github.com/microsoft/openapi.net
Affected ranges
- Type
- GIT
- Repo
- https://github.com/microsoft/openapi.net
- Events
-
IntroducedFixedIntroducedFixedIntroduced0 Unknown introduced commit / All previous commits are affectedFixed
- Database specific
-
Show details
{ "extracted_events": [ { "introduced": "2.0.0-preview.11" }, { "fixed": "2.12.0" }, { "introduced": "3.0.0" }, { "fixed": "3.10.0" }, { "introduced": "0" }, { "fixed": "1.6.30" } ], "source": "AFFECTED_FIELD" }