cve.bz

CVE-2026-72923 microsoft openapi.net: Uncontrolled Resource Consumption

7.5 highEPSS 1.8%Fix available

High (7.5) in microsoft openapi.net. EPSS 1.8% estimated probability of exploitation activity in the next 30 days. Fixed in Microsoft.OpenApi.YamlReader 2.12.0, 3.10.0.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
1.8% (unchanged from 1.8% a week ago; 1.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 79th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-09-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-400 Uncontrolled Resource Consumption
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • Microsoft.OpenApi.YamlReader (NuGet): fixed in 3.10.0, 2.12.0
  • Microsoft.OpenApi.Readers (NuGet): fixed in 1.6.30

Ask an AI about this CVE

Show the promptExplain CVE-2026-72923 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-72923?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-72923?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-72923 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
microsoft OpenAPI.NET>= 3.0.0, < 3.10.0
microsoft OpenAPI.NET>= 2.0.0-preview.11, < 2.12.0
microsoft OpenAPI.NET< 1.6.30

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-7pxr-59rr-hqj2NuGetMicrosoft.OpenApi.YamlReader>=3.0.0 <3.10.03.10.0
GHSA-7pxr-59rr-hqj2NuGetMicrosoft.OpenApi.YamlReader>=2.0.0-preview.11 <2.12.02.12.0
GHSA-7pxr-59rr-hqj2NuGetMicrosoft.OpenApi.Readers<1.6.301.6.30

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON