Microsoft.OpenApi
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
- 3w ago
- Total releases
- 163
- Cadence
- ~daily
- Last 12 months
- 59
Reach
- Stars
- 1.6k
Details
- License
- MIT
- First release
- Dec 14, 2017
| Version | Released | |
|---|---|---|
2.12.2
patch
| ||
1.6.31
patch
| ||
3.10.2
patch
| ||
2.12.1
patch
| ||
1.6.30
patch
| ||
2.12.0
minor
| ||
3.10.0
minor
| ||
2.11.0
minor
| ||
3.9.0
minor
| ||
2.10.0
minor
| ||
3.8.0
minor
| ||
2.9.0
minor
| ||
3.7.0
minor
| ||
2.8.0
minor
| ||
3.6.0
minor
| ||
3.5.5
patch
| ||
2.7.6
patch
| ||
2.7.5
patch
| ||
3.5.4
patch
| ||
2.7.4
patch
1 CVE
CVE-2026-49451
GHSA-v5pm-xwqc-g5wc
Jun 30, 2026
Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small OpenAPI document containing a circular schema reference can cause process termination through stack overflow in Microsoft.OpenApi. The issue affects OpenAPI document parsing through public OpenAPI.NET reader APIs and has been confirmed across both JSON and YAML reader paths. Affected versions
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted OpenAPI documents in-process may be terminated by a crafted OpenAPI document containing circular schema references. 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. DetailsA standalone isolated-process harness confirmed repeatable process termination through public OpenAPI.NET reader APIs. The issue reproduces in the affected released NuGet packages and affects both JSON and YAML reader paths. A separate Microsoft-owned local consumer, Example payloadRemediationUsers should upgrade to Microsoft.OpenApi 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
2.0.0
2.0.0-preview1
2.0.0-preview10
2.0.0-preview2
2.0.0-preview3
2.0.0-preview4
2.0.0-preview5
2.0.0-preview6
2.0.0-preview7
2.0.0-preview8
2.0.0-preview9
2.0.1
+ 42 more Show less
2.1.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
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
3.5.1
3.5.2
3.5.3
Fixed in
2.7.5
3.5.4
References Updated Jul 06, 2026 · Source: OSV.dev | ||
3.5.3
patch
1 CVE
CVE-2026-49451
GHSA-v5pm-xwqc-g5wc
Jun 30, 2026
Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small OpenAPI document containing a circular schema reference can cause process termination through stack overflow in Microsoft.OpenApi. The issue affects OpenAPI document parsing through public OpenAPI.NET reader APIs and has been confirmed across both JSON and YAML reader paths. Affected versions
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted OpenAPI documents in-process may be terminated by a crafted OpenAPI document containing circular schema references. 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. DetailsA standalone isolated-process harness confirmed repeatable process termination through public OpenAPI.NET reader APIs. The issue reproduces in the affected released NuGet packages and affects both JSON and YAML reader paths. A separate Microsoft-owned local consumer, Example payloadRemediationUsers should upgrade to Microsoft.OpenApi 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
2.0.0
2.0.0-preview1
2.0.0-preview10
2.0.0-preview2
2.0.0-preview3
2.0.0-preview4
2.0.0-preview5
2.0.0-preview6
2.0.0-preview7
2.0.0-preview8
2.0.0-preview9
2.0.1
+ 42 more Show less
2.1.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
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
3.5.1
3.5.2
3.5.3
Fixed in
2.7.5
3.5.4
References Updated Jul 06, 2026 · Source: OSV.dev | ||
1.6.29
patch
| ||
2.7.3
patch
1 CVE
CVE-2026-49451
GHSA-v5pm-xwqc-g5wc
Jun 30, 2026
Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small OpenAPI document containing a circular schema reference can cause process termination through stack overflow in Microsoft.OpenApi. The issue affects OpenAPI document parsing through public OpenAPI.NET reader APIs and has been confirmed across both JSON and YAML reader paths. Affected versions
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted OpenAPI documents in-process may be terminated by a crafted OpenAPI document containing circular schema references. 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. DetailsA standalone isolated-process harness confirmed repeatable process termination through public OpenAPI.NET reader APIs. The issue reproduces in the affected released NuGet packages and affects both JSON and YAML reader paths. A separate Microsoft-owned local consumer, Example payloadRemediationUsers should upgrade to Microsoft.OpenApi 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
2.0.0
2.0.0-preview1
2.0.0-preview10
2.0.0-preview2
2.0.0-preview3
2.0.0-preview4
2.0.0-preview5
2.0.0-preview6
2.0.0-preview7
2.0.0-preview8
2.0.0-preview9
2.0.1
+ 42 more Show less
2.1.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
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
3.5.1
3.5.2
3.5.3
Fixed in
2.7.5
3.5.4
References Updated Jul 06, 2026 · Source: OSV.dev | ||
3.5.2
patch
1 CVE
CVE-2026-49451
GHSA-v5pm-xwqc-g5wc
Jun 30, 2026
Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small OpenAPI document containing a circular schema reference can cause process termination through stack overflow in Microsoft.OpenApi. The issue affects OpenAPI document parsing through public OpenAPI.NET reader APIs and has been confirmed across both JSON and YAML reader paths. Affected versions
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted OpenAPI documents in-process may be terminated by a crafted OpenAPI document containing circular schema references. 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. DetailsA standalone isolated-process harness confirmed repeatable process termination through public OpenAPI.NET reader APIs. The issue reproduces in the affected released NuGet packages and affects both JSON and YAML reader paths. A separate Microsoft-owned local consumer, Example payloadRemediationUsers should upgrade to Microsoft.OpenApi 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
2.0.0
2.0.0-preview1
2.0.0-preview10
2.0.0-preview2
2.0.0-preview3
2.0.0-preview4
2.0.0-preview5
2.0.0-preview6
2.0.0-preview7
2.0.0-preview8
2.0.0-preview9
2.0.1
+ 42 more Show less
2.1.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
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
3.5.1
3.5.2
3.5.3
Fixed in
2.7.5
3.5.4
References Updated Jul 06, 2026 · Source: OSV.dev | ||
2.7.2
patch
1 CVE
CVE-2026-49451
GHSA-v5pm-xwqc-g5wc
Jun 30, 2026
Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small OpenAPI document containing a circular schema reference can cause process termination through stack overflow in Microsoft.OpenApi. The issue affects OpenAPI document parsing through public OpenAPI.NET reader APIs and has been confirmed across both JSON and YAML reader paths. Affected versions
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted OpenAPI documents in-process may be terminated by a crafted OpenAPI document containing circular schema references. 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. DetailsA standalone isolated-process harness confirmed repeatable process termination through public OpenAPI.NET reader APIs. The issue reproduces in the affected released NuGet packages and affects both JSON and YAML reader paths. A separate Microsoft-owned local consumer, Example payloadRemediationUsers should upgrade to Microsoft.OpenApi 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
2.0.0
2.0.0-preview1
2.0.0-preview10
2.0.0-preview2
2.0.0-preview3
2.0.0-preview4
2.0.0-preview5
2.0.0-preview6
2.0.0-preview7
2.0.0-preview8
2.0.0-preview9
2.0.1
+ 42 more Show less
2.1.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
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
3.5.1
3.5.2
3.5.3
Fixed in
2.7.5
3.5.4
References Updated Jul 06, 2026 · Source: OSV.dev | ||
3.5.1
patch
1 CVE
CVE-2026-49451
GHSA-v5pm-xwqc-g5wc
Jun 30, 2026
Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small OpenAPI document containing a circular schema reference can cause process termination through stack overflow in Microsoft.OpenApi. The issue affects OpenAPI document parsing through public OpenAPI.NET reader APIs and has been confirmed across both JSON and YAML reader paths. Affected versions
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted OpenAPI documents in-process may be terminated by a crafted OpenAPI document containing circular schema references. 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. DetailsA standalone isolated-process harness confirmed repeatable process termination through public OpenAPI.NET reader APIs. The issue reproduces in the affected released NuGet packages and affects both JSON and YAML reader paths. A separate Microsoft-owned local consumer, Example payloadRemediationUsers should upgrade to Microsoft.OpenApi 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
2.0.0
2.0.0-preview1
2.0.0-preview10
2.0.0-preview2
2.0.0-preview3
2.0.0-preview4
2.0.0-preview5
2.0.0-preview6
2.0.0-preview7
2.0.0-preview8
2.0.0-preview9
2.0.1
+ 42 more Show less
2.1.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
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
3.5.1
3.5.2
3.5.3
Fixed in
2.7.5
3.5.4
References Updated Jul 06, 2026 · Source: OSV.dev | ||
3.5.0
minor
1 CVE
CVE-2026-49451
GHSA-v5pm-xwqc-g5wc
Jun 30, 2026
Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small OpenAPI document containing a circular schema reference can cause process termination through stack overflow in Microsoft.OpenApi. The issue affects OpenAPI document parsing through public OpenAPI.NET reader APIs and has been confirmed across both JSON and YAML reader paths. Affected versions
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted OpenAPI documents in-process may be terminated by a crafted OpenAPI document containing circular schema references. 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. DetailsA standalone isolated-process harness confirmed repeatable process termination through public OpenAPI.NET reader APIs. The issue reproduces in the affected released NuGet packages and affects both JSON and YAML reader paths. A separate Microsoft-owned local consumer, Example payloadRemediationUsers should upgrade to Microsoft.OpenApi 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
2.0.0
2.0.0-preview1
2.0.0-preview10
2.0.0-preview2
2.0.0-preview3
2.0.0-preview4
2.0.0-preview5
2.0.0-preview6
2.0.0-preview7
2.0.0-preview8
2.0.0-preview9
2.0.1
+ 42 more Show less
2.1.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
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
3.5.1
3.5.2
3.5.3
Fixed in
2.7.5
3.5.4
References Updated Jul 06, 2026 · Source: OSV.dev | ||
2.7.1
patch
1 CVE
CVE-2026-49451
GHSA-v5pm-xwqc-g5wc
Jun 30, 2026
Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small OpenAPI document containing a circular schema reference can cause process termination through stack overflow in Microsoft.OpenApi. The issue affects OpenAPI document parsing through public OpenAPI.NET reader APIs and has been confirmed across both JSON and YAML reader paths. Affected versions
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted OpenAPI documents in-process may be terminated by a crafted OpenAPI document containing circular schema references. 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. DetailsA standalone isolated-process harness confirmed repeatable process termination through public OpenAPI.NET reader APIs. The issue reproduces in the affected released NuGet packages and affects both JSON and YAML reader paths. A separate Microsoft-owned local consumer, Example payloadRemediationUsers should upgrade to Microsoft.OpenApi 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
2.0.0
2.0.0-preview1
2.0.0-preview10
2.0.0-preview2
2.0.0-preview3
2.0.0-preview4
2.0.0-preview5
2.0.0-preview6
2.0.0-preview7
2.0.0-preview8
2.0.0-preview9
2.0.1
+ 42 more Show less
2.1.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
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
3.5.1
3.5.2
3.5.3
Fixed in
2.7.5
3.5.4
References Updated Jul 06, 2026 · Source: OSV.dev | ||
2.7.0
minor
1 CVE
CVE-2026-49451
GHSA-v5pm-xwqc-g5wc
Jun 30, 2026
Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small OpenAPI document containing a circular schema reference can cause process termination through stack overflow in Microsoft.OpenApi. The issue affects OpenAPI document parsing through public OpenAPI.NET reader APIs and has been confirmed across both JSON and YAML reader paths. Affected versions
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted OpenAPI documents in-process may be terminated by a crafted OpenAPI document containing circular schema references. 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. DetailsA standalone isolated-process harness confirmed repeatable process termination through public OpenAPI.NET reader APIs. The issue reproduces in the affected released NuGet packages and affects both JSON and YAML reader paths. A separate Microsoft-owned local consumer, Example payloadRemediationUsers should upgrade to Microsoft.OpenApi 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
2.0.0
2.0.0-preview1
2.0.0-preview10
2.0.0-preview2
2.0.0-preview3
2.0.0-preview4
2.0.0-preview5
2.0.0-preview6
2.0.0-preview7
2.0.0-preview8
2.0.0-preview9
2.0.1
+ 42 more Show less
2.1.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
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
3.5.1
3.5.2
3.5.3
Fixed in
2.7.5
3.5.4
References Updated Jul 06, 2026 · Source: OSV.dev | ||
3.4.0
minor
1 CVE
CVE-2026-49451
GHSA-v5pm-xwqc-g5wc
Jun 30, 2026
Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small OpenAPI document containing a circular schema reference can cause process termination through stack overflow in Microsoft.OpenApi. The issue affects OpenAPI document parsing through public OpenAPI.NET reader APIs and has been confirmed across both JSON and YAML reader paths. Affected versions
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted OpenAPI documents in-process may be terminated by a crafted OpenAPI document containing circular schema references. 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. DetailsA standalone isolated-process harness confirmed repeatable process termination through public OpenAPI.NET reader APIs. The issue reproduces in the affected released NuGet packages and affects both JSON and YAML reader paths. A separate Microsoft-owned local consumer, Example payloadRemediationUsers should upgrade to Microsoft.OpenApi 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
2.0.0
2.0.0-preview1
2.0.0-preview10
2.0.0-preview2
2.0.0-preview3
2.0.0-preview4
2.0.0-preview5
2.0.0-preview6
2.0.0-preview7
2.0.0-preview8
2.0.0-preview9
2.0.1
+ 42 more Show less
2.1.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
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
3.5.1
3.5.2
3.5.3
Fixed in
2.7.5
3.5.4
References Updated Jul 06, 2026 · Source: OSV.dev | ||
2.6.1
patch
1 CVE
CVE-2026-49451
GHSA-v5pm-xwqc-g5wc
Jun 30, 2026
Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small OpenAPI document containing a circular schema reference can cause process termination through stack overflow in Microsoft.OpenApi. The issue affects OpenAPI document parsing through public OpenAPI.NET reader APIs and has been confirmed across both JSON and YAML reader paths. Affected versions
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted OpenAPI documents in-process may be terminated by a crafted OpenAPI document containing circular schema references. 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. DetailsA standalone isolated-process harness confirmed repeatable process termination through public OpenAPI.NET reader APIs. The issue reproduces in the affected released NuGet packages and affects both JSON and YAML reader paths. A separate Microsoft-owned local consumer, Example payloadRemediationUsers should upgrade to Microsoft.OpenApi 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
2.0.0
2.0.0-preview1
2.0.0-preview10
2.0.0-preview2
2.0.0-preview3
2.0.0-preview4
2.0.0-preview5
2.0.0-preview6
2.0.0-preview7
2.0.0-preview8
2.0.0-preview9
2.0.1
+ 42 more Show less
2.1.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
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
3.5.1
3.5.2
3.5.3
Fixed in
2.7.5
3.5.4
References Updated Jul 06, 2026 · Source: OSV.dev | ||
3.3.1
patch
1 CVE
CVE-2026-49451
GHSA-v5pm-xwqc-g5wc
Jun 30, 2026
Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small OpenAPI document containing a circular schema reference can cause process termination through stack overflow in Microsoft.OpenApi. The issue affects OpenAPI document parsing through public OpenAPI.NET reader APIs and has been confirmed across both JSON and YAML reader paths. Affected versions
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted OpenAPI documents in-process may be terminated by a crafted OpenAPI document containing circular schema references. 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. DetailsA standalone isolated-process harness confirmed repeatable process termination through public OpenAPI.NET reader APIs. The issue reproduces in the affected released NuGet packages and affects both JSON and YAML reader paths. A separate Microsoft-owned local consumer, Example payloadRemediationUsers should upgrade to Microsoft.OpenApi 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
2.0.0
2.0.0-preview1
2.0.0-preview10
2.0.0-preview2
2.0.0-preview3
2.0.0-preview4
2.0.0-preview5
2.0.0-preview6
2.0.0-preview7
2.0.0-preview8
2.0.0-preview9
2.0.1
+ 42 more Show less
2.1.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
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
3.5.1
3.5.2
3.5.3
Fixed in
2.7.5
3.5.4
References Updated Jul 06, 2026 · Source: OSV.dev | ||
2.6.0
minor
1 CVE
CVE-2026-49451
GHSA-v5pm-xwqc-g5wc
Jun 30, 2026
Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small OpenAPI document containing a circular schema reference can cause process termination through stack overflow in Microsoft.OpenApi. The issue affects OpenAPI document parsing through public OpenAPI.NET reader APIs and has been confirmed across both JSON and YAML reader paths. Affected versions
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted OpenAPI documents in-process may be terminated by a crafted OpenAPI document containing circular schema references. 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. DetailsA standalone isolated-process harness confirmed repeatable process termination through public OpenAPI.NET reader APIs. The issue reproduces in the affected released NuGet packages and affects both JSON and YAML reader paths. A separate Microsoft-owned local consumer, Example payloadRemediationUsers should upgrade to Microsoft.OpenApi 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
2.0.0
2.0.0-preview1
2.0.0-preview10
2.0.0-preview2
2.0.0-preview3
2.0.0-preview4
2.0.0-preview5
2.0.0-preview6
2.0.0-preview7
2.0.0-preview8
2.0.0-preview9
2.0.1
+ 42 more Show less
2.1.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
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
3.5.1
3.5.2
3.5.3
Fixed in
2.7.5
3.5.4
References Updated Jul 06, 2026 · Source: OSV.dev | ||
3.3.0
minor
1 CVE
CVE-2026-49451
GHSA-v5pm-xwqc-g5wc
Jun 30, 2026
Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small OpenAPI document containing a circular schema reference can cause process termination through stack overflow in Microsoft.OpenApi. The issue affects OpenAPI document parsing through public OpenAPI.NET reader APIs and has been confirmed across both JSON and YAML reader paths. Affected versions
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted OpenAPI documents in-process may be terminated by a crafted OpenAPI document containing circular schema references. 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. DetailsA standalone isolated-process harness confirmed repeatable process termination through public OpenAPI.NET reader APIs. The issue reproduces in the affected released NuGet packages and affects both JSON and YAML reader paths. A separate Microsoft-owned local consumer, Example payloadRemediationUsers should upgrade to Microsoft.OpenApi 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
2.0.0
2.0.0-preview1
2.0.0-preview10
2.0.0-preview2
2.0.0-preview3
2.0.0-preview4
2.0.0-preview5
2.0.0-preview6
2.0.0-preview7
2.0.0-preview8
2.0.0-preview9
2.0.1
+ 42 more Show less
2.1.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
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
3.5.1
3.5.2
3.5.3
Fixed in
2.7.5
3.5.4
References Updated Jul 06, 2026 · Source: OSV.dev | ||
2.5.0
minor
1 CVE
CVE-2026-49451
GHSA-v5pm-xwqc-g5wc
Jun 30, 2026
Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small OpenAPI document containing a circular schema reference can cause process termination through stack overflow in Microsoft.OpenApi. The issue affects OpenAPI document parsing through public OpenAPI.NET reader APIs and has been confirmed across both JSON and YAML reader paths. Affected versions
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted OpenAPI documents in-process may be terminated by a crafted OpenAPI document containing circular schema references. 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. DetailsA standalone isolated-process harness confirmed repeatable process termination through public OpenAPI.NET reader APIs. The issue reproduces in the affected released NuGet packages and affects both JSON and YAML reader paths. A separate Microsoft-owned local consumer, Example payloadRemediationUsers should upgrade to Microsoft.OpenApi 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
2.0.0
2.0.0-preview1
2.0.0-preview10
2.0.0-preview2
2.0.0-preview3
2.0.0-preview4
2.0.0-preview5
2.0.0-preview6
2.0.0-preview7
2.0.0-preview8
2.0.0-preview9
2.0.1
+ 42 more Show less
2.1.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
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
3.5.1
3.5.2
3.5.3
Fixed in
2.7.5
3.5.4
References Updated Jul 06, 2026 · Source: OSV.dev | ||
3.2.0
minor
1 CVE
CVE-2026-49451
GHSA-v5pm-xwqc-g5wc
Jun 30, 2026
Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small OpenAPI document containing a circular schema reference can cause process termination through stack overflow in Microsoft.OpenApi. The issue affects OpenAPI document parsing through public OpenAPI.NET reader APIs and has been confirmed across both JSON and YAML reader paths. Affected versions
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted OpenAPI documents in-process may be terminated by a crafted OpenAPI document containing circular schema references. 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. DetailsA standalone isolated-process harness confirmed repeatable process termination through public OpenAPI.NET reader APIs. The issue reproduces in the affected released NuGet packages and affects both JSON and YAML reader paths. A separate Microsoft-owned local consumer, Example payloadRemediationUsers should upgrade to Microsoft.OpenApi 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
2.0.0
2.0.0-preview1
2.0.0-preview10
2.0.0-preview2
2.0.0-preview3
2.0.0-preview4
2.0.0-preview5
2.0.0-preview6
2.0.0-preview7
2.0.0-preview8
2.0.0-preview9
2.0.1
+ 42 more Show less
2.1.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
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
3.5.1
3.5.2
3.5.3
Fixed in
2.7.5
3.5.4
References Updated Jul 06, 2026 · Source: OSV.dev | ||
3.1.3
patch
1 CVE
CVE-2026-49451
GHSA-v5pm-xwqc-g5wc
Jun 30, 2026
Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small OpenAPI document containing a circular schema reference can cause process termination through stack overflow in Microsoft.OpenApi. The issue affects OpenAPI document parsing through public OpenAPI.NET reader APIs and has been confirmed across both JSON and YAML reader paths. Affected versions
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted OpenAPI documents in-process may be terminated by a crafted OpenAPI document containing circular schema references. 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. DetailsA standalone isolated-process harness confirmed repeatable process termination through public OpenAPI.NET reader APIs. The issue reproduces in the affected released NuGet packages and affects both JSON and YAML reader paths. A separate Microsoft-owned local consumer, Example payloadRemediationUsers should upgrade to Microsoft.OpenApi 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
2.0.0
2.0.0-preview1
2.0.0-preview10
2.0.0-preview2
2.0.0-preview3
2.0.0-preview4
2.0.0-preview5
2.0.0-preview6
2.0.0-preview7
2.0.0-preview8
2.0.0-preview9
2.0.1
+ 42 more Show less
2.1.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
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
3.5.1
3.5.2
3.5.3
Fixed in
2.7.5
3.5.4
References Updated Jul 06, 2026 · Source: OSV.dev | ||
2.4.3
patch
1 CVE
CVE-2026-49451
GHSA-v5pm-xwqc-g5wc
Jun 30, 2026
Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small OpenAPI document containing a circular schema reference can cause process termination through stack overflow in Microsoft.OpenApi. The issue affects OpenAPI document parsing through public OpenAPI.NET reader APIs and has been confirmed across both JSON and YAML reader paths. Affected versions
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted OpenAPI documents in-process may be terminated by a crafted OpenAPI document containing circular schema references. 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. DetailsA standalone isolated-process harness confirmed repeatable process termination through public OpenAPI.NET reader APIs. The issue reproduces in the affected released NuGet packages and affects both JSON and YAML reader paths. A separate Microsoft-owned local consumer, Example payloadRemediationUsers should upgrade to Microsoft.OpenApi 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
2.0.0
2.0.0-preview1
2.0.0-preview10
2.0.0-preview2
2.0.0-preview3
2.0.0-preview4
2.0.0-preview5
2.0.0-preview6
2.0.0-preview7
2.0.0-preview8
2.0.0-preview9
2.0.1
+ 42 more Show less
2.1.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
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
3.5.1
3.5.2
3.5.3
Fixed in
2.7.5
3.5.4
References Updated Jul 06, 2026 · Source: OSV.dev | ||
2.4.2
patch
1 CVE
CVE-2026-49451
GHSA-v5pm-xwqc-g5wc
Jun 30, 2026
Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small OpenAPI document containing a circular schema reference can cause process termination through stack overflow in Microsoft.OpenApi. The issue affects OpenAPI document parsing through public OpenAPI.NET reader APIs and has been confirmed across both JSON and YAML reader paths. Affected versions
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted OpenAPI documents in-process may be terminated by a crafted OpenAPI document containing circular schema references. 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. DetailsA standalone isolated-process harness confirmed repeatable process termination through public OpenAPI.NET reader APIs. The issue reproduces in the affected released NuGet packages and affects both JSON and YAML reader paths. A separate Microsoft-owned local consumer, Example payloadRemediationUsers should upgrade to Microsoft.OpenApi 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
2.0.0
2.0.0-preview1
2.0.0-preview10
2.0.0-preview2
2.0.0-preview3
2.0.0-preview4
2.0.0-preview5
2.0.0-preview6
2.0.0-preview7
2.0.0-preview8
2.0.0-preview9
2.0.1
+ 42 more Show less
2.1.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
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
3.5.1
3.5.2
3.5.3
Fixed in
2.7.5
3.5.4
References Updated Jul 06, 2026 · Source: OSV.dev | ||
3.1.2
patch
1 CVE
CVE-2026-49451
GHSA-v5pm-xwqc-g5wc
Jun 30, 2026
Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small OpenAPI document containing a circular schema reference can cause process termination through stack overflow in Microsoft.OpenApi. The issue affects OpenAPI document parsing through public OpenAPI.NET reader APIs and has been confirmed across both JSON and YAML reader paths. Affected versions
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted OpenAPI documents in-process may be terminated by a crafted OpenAPI document containing circular schema references. 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. DetailsA standalone isolated-process harness confirmed repeatable process termination through public OpenAPI.NET reader APIs. The issue reproduces in the affected released NuGet packages and affects both JSON and YAML reader paths. A separate Microsoft-owned local consumer, Example payloadRemediationUsers should upgrade to Microsoft.OpenApi 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
2.0.0
2.0.0-preview1
2.0.0-preview10
2.0.0-preview2
2.0.0-preview3
2.0.0-preview4
2.0.0-preview5
2.0.0-preview6
2.0.0-preview7
2.0.0-preview8
2.0.0-preview9
2.0.1
+ 42 more Show less
2.1.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
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
3.5.1
3.5.2
3.5.3
Fixed in
2.7.5
3.5.4
References Updated Jul 06, 2026 · Source: OSV.dev | ||
3.1.1
minor
1 CVE
CVE-2026-49451
GHSA-v5pm-xwqc-g5wc
Jun 30, 2026
Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small OpenAPI document containing a circular schema reference can cause process termination through stack overflow in Microsoft.OpenApi. The issue affects OpenAPI document parsing through public OpenAPI.NET reader APIs and has been confirmed across both JSON and YAML reader paths. Affected versions
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted OpenAPI documents in-process may be terminated by a crafted OpenAPI document containing circular schema references. 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. DetailsA standalone isolated-process harness confirmed repeatable process termination through public OpenAPI.NET reader APIs. The issue reproduces in the affected released NuGet packages and affects both JSON and YAML reader paths. A separate Microsoft-owned local consumer, Example payloadRemediationUsers should upgrade to Microsoft.OpenApi 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
2.0.0
2.0.0-preview1
2.0.0-preview10
2.0.0-preview2
2.0.0-preview3
2.0.0-preview4
2.0.0-preview5
2.0.0-preview6
2.0.0-preview7
2.0.0-preview8
2.0.0-preview9
2.0.1
+ 42 more Show less
2.1.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
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
3.5.1
3.5.2
3.5.3
Fixed in
2.7.5
3.5.4
References Updated Jul 06, 2026 · Source: OSV.dev | ||
2.4.1
patch
1 CVE
CVE-2026-49451
GHSA-v5pm-xwqc-g5wc
Jun 30, 2026
Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small OpenAPI document containing a circular schema reference can cause process termination through stack overflow in Microsoft.OpenApi. The issue affects OpenAPI document parsing through public OpenAPI.NET reader APIs and has been confirmed across both JSON and YAML reader paths. Affected versions
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted OpenAPI documents in-process may be terminated by a crafted OpenAPI document containing circular schema references. 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. DetailsA standalone isolated-process harness confirmed repeatable process termination through public OpenAPI.NET reader APIs. The issue reproduces in the affected released NuGet packages and affects both JSON and YAML reader paths. A separate Microsoft-owned local consumer, Example payloadRemediationUsers should upgrade to Microsoft.OpenApi 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
2.0.0
2.0.0-preview1
2.0.0-preview10
2.0.0-preview2
2.0.0-preview3
2.0.0-preview4
2.0.0-preview5
2.0.0-preview6
2.0.0-preview7
2.0.0-preview8
2.0.0-preview9
2.0.1
+ 42 more Show less
2.1.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
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
3.5.1
3.5.2
3.5.3
Fixed in
2.7.5
3.5.4
References Updated Jul 06, 2026 · Source: OSV.dev | ||
2.4.0
minor
1 CVE
CVE-2026-49451
GHSA-v5pm-xwqc-g5wc
Jun 30, 2026
Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small OpenAPI document containing a circular schema reference can cause process termination through stack overflow in Microsoft.OpenApi. The issue affects OpenAPI document parsing through public OpenAPI.NET reader APIs and has been confirmed across both JSON and YAML reader paths. Affected versions
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted OpenAPI documents in-process may be terminated by a crafted OpenAPI document containing circular schema references. 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. DetailsA standalone isolated-process harness confirmed repeatable process termination through public OpenAPI.NET reader APIs. The issue reproduces in the affected released NuGet packages and affects both JSON and YAML reader paths. A separate Microsoft-owned local consumer, Example payloadRemediationUsers should upgrade to Microsoft.OpenApi 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
2.0.0
2.0.0-preview1
2.0.0-preview10
2.0.0-preview2
2.0.0-preview3
2.0.0-preview4
2.0.0-preview5
2.0.0-preview6
2.0.0-preview7
2.0.0-preview8
2.0.0-preview9
2.0.1
+ 42 more Show less
2.1.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
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
3.5.1
3.5.2
3.5.3
Fixed in
2.7.5
3.5.4
References Updated Jul 06, 2026 · Source: OSV.dev | ||
3.0.3
patch
1 CVE
CVE-2026-49451
GHSA-v5pm-xwqc-g5wc
Jun 30, 2026
Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small OpenAPI document containing a circular schema reference can cause process termination through stack overflow in Microsoft.OpenApi. The issue affects OpenAPI document parsing through public OpenAPI.NET reader APIs and has been confirmed across both JSON and YAML reader paths. Affected versions
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted OpenAPI documents in-process may be terminated by a crafted OpenAPI document containing circular schema references. 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. DetailsA standalone isolated-process harness confirmed repeatable process termination through public OpenAPI.NET reader APIs. The issue reproduces in the affected released NuGet packages and affects both JSON and YAML reader paths. A separate Microsoft-owned local consumer, Example payloadRemediationUsers should upgrade to Microsoft.OpenApi 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
2.0.0
2.0.0-preview1
2.0.0-preview10
2.0.0-preview2
2.0.0-preview3
2.0.0-preview4
2.0.0-preview5
2.0.0-preview6
2.0.0-preview7
2.0.0-preview8
2.0.0-preview9
2.0.1
+ 42 more Show less
2.1.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
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
3.5.1
3.5.2
3.5.3
Fixed in
2.7.5
3.5.4
References Updated Jul 06, 2026 · Source: OSV.dev | ||
2.3.12
patch
1 CVE
CVE-2026-49451
GHSA-v5pm-xwqc-g5wc
Jun 30, 2026
Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small OpenAPI document containing a circular schema reference can cause process termination through stack overflow in Microsoft.OpenApi. The issue affects OpenAPI document parsing through public OpenAPI.NET reader APIs and has been confirmed across both JSON and YAML reader paths. Affected versions
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted OpenAPI documents in-process may be terminated by a crafted OpenAPI document containing circular schema references. 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. DetailsA standalone isolated-process harness confirmed repeatable process termination through public OpenAPI.NET reader APIs. The issue reproduces in the affected released NuGet packages and affects both JSON and YAML reader paths. A separate Microsoft-owned local consumer, Example payloadRemediationUsers should upgrade to Microsoft.OpenApi 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
2.0.0
2.0.0-preview1
2.0.0-preview10
2.0.0-preview2
2.0.0-preview3
2.0.0-preview4
2.0.0-preview5
2.0.0-preview6
2.0.0-preview7
2.0.0-preview8
2.0.0-preview9
2.0.1
+ 42 more Show less
2.1.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
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
3.5.1
3.5.2
3.5.3
Fixed in
2.7.5
3.5.4
References Updated Jul 06, 2026 · Source: OSV.dev | ||
2.3.11
patch
1 CVE
CVE-2026-49451
GHSA-v5pm-xwqc-g5wc
Jun 30, 2026
Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small OpenAPI document containing a circular schema reference can cause process termination through stack overflow in Microsoft.OpenApi. The issue affects OpenAPI document parsing through public OpenAPI.NET reader APIs and has been confirmed across both JSON and YAML reader paths. Affected versions
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted OpenAPI documents in-process may be terminated by a crafted OpenAPI document containing circular schema references. 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. DetailsA standalone isolated-process harness confirmed repeatable process termination through public OpenAPI.NET reader APIs. The issue reproduces in the affected released NuGet packages and affects both JSON and YAML reader paths. A separate Microsoft-owned local consumer, Example payloadRemediationUsers should upgrade to Microsoft.OpenApi 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
2.0.0
2.0.0-preview1
2.0.0-preview10
2.0.0-preview2
2.0.0-preview3
2.0.0-preview4
2.0.0-preview5
2.0.0-preview6
2.0.0-preview7
2.0.0-preview8
2.0.0-preview9
2.0.1
+ 42 more Show less
2.1.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
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
3.5.1
3.5.2
3.5.3
Fixed in
2.7.5
3.5.4
References Updated Jul 06, 2026 · Source: OSV.dev | ||
3.0.2
patch
1 CVE
CVE-2026-49451
GHSA-v5pm-xwqc-g5wc
Jun 30, 2026
Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small OpenAPI document containing a circular schema reference can cause process termination through stack overflow in Microsoft.OpenApi. The issue affects OpenAPI document parsing through public OpenAPI.NET reader APIs and has been confirmed across both JSON and YAML reader paths. Affected versions
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted OpenAPI documents in-process may be terminated by a crafted OpenAPI document containing circular schema references. 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. DetailsA standalone isolated-process harness confirmed repeatable process termination through public OpenAPI.NET reader APIs. The issue reproduces in the affected released NuGet packages and affects both JSON and YAML reader paths. A separate Microsoft-owned local consumer, Example payloadRemediationUsers should upgrade to Microsoft.OpenApi 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
2.0.0
2.0.0-preview1
2.0.0-preview10
2.0.0-preview2
2.0.0-preview3
2.0.0-preview4
2.0.0-preview5
2.0.0-preview6
2.0.0-preview7
2.0.0-preview8
2.0.0-preview9
2.0.1
+ 42 more Show less
2.1.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
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
3.5.1
3.5.2
3.5.3
Fixed in
2.7.5
3.5.4
References Updated Jul 06, 2026 · Source: OSV.dev | ||
2.3.10
patch
1 CVE
CVE-2026-49451
GHSA-v5pm-xwqc-g5wc
Jun 30, 2026
Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small OpenAPI document containing a circular schema reference can cause process termination through stack overflow in Microsoft.OpenApi. The issue affects OpenAPI document parsing through public OpenAPI.NET reader APIs and has been confirmed across both JSON and YAML reader paths. Affected versions
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted OpenAPI documents in-process may be terminated by a crafted OpenAPI document containing circular schema references. 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. DetailsA standalone isolated-process harness confirmed repeatable process termination through public OpenAPI.NET reader APIs. The issue reproduces in the affected released NuGet packages and affects both JSON and YAML reader paths. A separate Microsoft-owned local consumer, Example payloadRemediationUsers should upgrade to Microsoft.OpenApi 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
2.0.0
2.0.0-preview1
2.0.0-preview10
2.0.0-preview2
2.0.0-preview3
2.0.0-preview4
2.0.0-preview5
2.0.0-preview6
2.0.0-preview7
2.0.0-preview8
2.0.0-preview9
2.0.1
+ 42 more Show less
2.1.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
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
3.5.1
3.5.2
3.5.3
Fixed in
2.7.5
3.5.4
References Updated Jul 06, 2026 · Source: OSV.dev | ||
3.0.1
patch
1 CVE
CVE-2026-49451
GHSA-v5pm-xwqc-g5wc
Jun 30, 2026
Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small OpenAPI document containing a circular schema reference can cause process termination through stack overflow in Microsoft.OpenApi. The issue affects OpenAPI document parsing through public OpenAPI.NET reader APIs and has been confirmed across both JSON and YAML reader paths. Affected versions
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted OpenAPI documents in-process may be terminated by a crafted OpenAPI document containing circular schema references. 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. DetailsA standalone isolated-process harness confirmed repeatable process termination through public OpenAPI.NET reader APIs. The issue reproduces in the affected released NuGet packages and affects both JSON and YAML reader paths. A separate Microsoft-owned local consumer, Example payloadRemediationUsers should upgrade to Microsoft.OpenApi 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
2.0.0
2.0.0-preview1
2.0.0-preview10
2.0.0-preview2
2.0.0-preview3
2.0.0-preview4
2.0.0-preview5
2.0.0-preview6
2.0.0-preview7
2.0.0-preview8
2.0.0-preview9
2.0.1
+ 42 more Show less
2.1.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
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
3.5.1
3.5.2
3.5.3
Fixed in
2.7.5
3.5.4
References Updated Jul 06, 2026 · Source: OSV.dev | ||
3.0.0
major
1 CVE
CVE-2026-49451
GHSA-v5pm-xwqc-g5wc
Jun 30, 2026
Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactA small OpenAPI document containing a circular schema reference can cause process termination through stack overflow in Microsoft.OpenApi. The issue affects OpenAPI document parsing through public OpenAPI.NET reader APIs and has been confirmed across both JSON and YAML reader paths. Affected versions
Patches
ImpactApplications, CLIs, developer tools, or services that parse untrusted OpenAPI documents in-process may be terminated by a crafted OpenAPI document containing circular schema references. 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. DetailsA standalone isolated-process harness confirmed repeatable process termination through public OpenAPI.NET reader APIs. The issue reproduces in the affected released NuGet packages and affects both JSON and YAML reader paths. A separate Microsoft-owned local consumer, Example payloadRemediationUsers should upgrade to Microsoft.OpenApi 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
2.0.0
2.0.0-preview1
2.0.0-preview10
2.0.0-preview2
2.0.0-preview3
2.0.0-preview4
2.0.0-preview5
2.0.0-preview6
2.0.0-preview7
2.0.0-preview8
2.0.0-preview9
2.0.1
+ 42 more Show less
2.1.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
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
3.5.1
3.5.2
3.5.3
Fixed in
2.7.5
3.5.4
References Updated Jul 06, 2026 · Source: OSV.dev |