Microsoft.OpenApi.YamlReader
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.
View on Github
Activity
- Latest release
- 1w ago
- Total releases
- 80
- Cadence
- ~daily
- Last 12 months
- 50
Reach
- Stars
- 1.6k
Details
- License
- MIT
- First release
- Mar 18, 2025
| Version | Released | |
|---|---|---|
3.11.0
minor
| ||
2.13.0
minor
| ||
2.12.2
patch
| ||
3.10.2
patch
| ||
2.12.1
patch
| ||
2.12.0
minor
| ||
3.10.0
minor
| ||
2.11.0
minor
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
3.9.0
minor
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
2.10.0
minor
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
3.8.0
minor
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
2.9.0
minor
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
3.7.0
minor
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
2.8.0
minor
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
3.6.0
minor
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
3.5.5
patch
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
2.7.6
patch
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
2.7.5
patch
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
3.5.4
patch
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
3.5.3
patch
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
2.7.4
patch
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
2.7.3
patch
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
3.5.2
patch
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
2.7.2
patch
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
3.5.1
patch
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
3.5.0
minor
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
2.7.1
patch
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
2.7.0
minor
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
3.4.0
minor
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
2.6.1
patch
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
3.3.1
patch
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
2.6.0
minor
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
3.3.0
minor
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
2.5.0
minor
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
3.2.0
minor
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
3.1.3
patch
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
2.4.3
patch
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
2.4.2
patch
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
3.1.2
patch
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
3.1.1
minor
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
2.4.1
patch
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
2.4.0
minor
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
3.0.3
patch
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
2.3.12
patch
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
2.3.11
patch
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
3.0.2
patch
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
2.3.10
patch
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
3.0.1
patch
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
3.0.0
major
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev | ||
2.3.9
patch
1 CVE
CVE-2026-72923
GHSA-7pxr-59rr-hqj2
Oct 14, 2026
Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small YAML OpenAPI document containing nested anchors and aliases can cause uncontrolled resource consumption in Microsoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers. The issue affects OpenAPI document parsing through the public YAML reader APIs and can cause the parsing process to allocate excessive memory and terminate through out-of-memory conditions. Affected versionsMicrosoft.OpenApi.YamlReader
Microsoft.OpenApi.Readers
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted YAML OpenAPI documents in-process may be terminated by a crafted YAML document containing nested anchors and aliases. The impact is availability/process termination only. This report does not claim remote code execution, authentication bypass, credential exposure, privilege escalation, data exposure, or Microsoft hosted service impact. DetailsMicrosoft.OpenApi.YamlReader and Microsoft.OpenApi.Readers parses YAML through SharpYaml. SharpYaml represents aliases as shared Without a bound on that conversion work, a small YAML document using nested anchors and aliases can expand exponentially during conversion. With This is an uncontrolled resource consumption vulnerability, also known as a "billion laughs" style denial of service. Example payloadRemediationUsers should upgrade to Microsoft.OpenApi.YamlReader The patched versions bound YAML-to-JSON conversion work and fail fast instead of allowing unbounded expansion. The default limits are:
When the limits are exceeded, The limits are exposed as process-wide static properties on
Applications that parse OpenAPI documents from untrusted sources should avoid parsing those documents in the primary application process when possible. Running parsing in an isolated process can reduce the blast radius of parser failures. Affected versions
3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2
3.1.3
3.2.0
3.3.0
3.3.1
3.4.0
3.5.0
+ 44 more Show less
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.6.0
3.7.0
3.8.0
3.9.0
2.0.0
2.0.1
2.1.0
2.10.0
2.11.0
2.2.0
2.3.0
2.3.1
2.3.10
2.3.11
2.3.12
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.1
2.4.2
2.4.3
2.5.0
2.6.0
2.6.1
2.7.0
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.8.0
2.9.0
Fixed in
2.12.0
3.10.0
References
Updated Oct 14, 2026 · Source: OSV.dev |