CVE-2026-72923
Last modified
CVE-2026-72923 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. 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. EPSS estimates a 1.20% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Microsoft | OpenApi.YamlReader | >= 2.0.0-preview.11, < 2.12.0; >= 3.0.0, < 3.10.0 |
| Microsoft | OpenApi.Readers | < 1.6.30 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-72923?
How severe is CVE-2026-72923?
How do I fix CVE-2026-72923?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-72918Rocket.Chat is an open-source, secure, fully customizable co…5.4
- CVE-2026-72919Rocket.Chat is an open-source, secure, fully customizable co…4.3
- CVE-2026-7292A security vulnerability has been detected in o2oa up to 10.…5.6
- CVE-2026-72920SeaweedFS is a distributed storage system. Prior to 4.24, th…9.8
- CVE-2026-72921SeaweedFS is a distributed storage system. Prior to 4.24, th…8.1
- CVE-2026-72922AutoGPT is a workflow automation platform for creating, depl…8.2
- CVE-2026-72924GitHub CLI (gh) is GitHub's official command line tool. Vers…2.1
- CVE-2026-72925SWC is a TypeScript / JavaScript compiler written in Rust. P…6.1
- CVE-2026-72926Use after free in Windows Internet Connection Sharing (ICS) …7
- CVE-2026-72927Heap-based buffer overflow in Winsock allows an authorized a…7.8
- CVE-2026-72928Use after free in Windows DNS allows an authorized attacker …7.5
- CVE-2026-72929Improper validation of integrity check value in Windows Inst…7.8
Are you affected by CVE-2026-72923?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
