VulnerabilityPublished 30 Jun 2026

CVE-2026-49451: microsoft OpenAPI.NET · Uncontrolled Recursion

Affects microsoft OpenAPI.NETSource CVE Database V5

Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 3.5.4 or 2.7.5 soon.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.5.4, 2.7.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade OpenAPI.NET to 3.5.4 or 2.7.5; microsoft.openapi.net to 3.5.4.

Affected software

Product	Affected	Fixed in
microsoftOpenAPI.NET	Affected >=3.0.0 <3.5.4	Fixed in 3.5.4
microsoftOpenAPI.NET	Affected >=2.0.0-preview11 <2.7.5	Fixed in 2.7.5
NuGetmicrosoft.openapi.net`pkg:nuget/microsoft.openapi.net`Other threats	Affected >=3.0.0 <3.5.4	Fixed in 3.5.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to Microsoft OpenAPI.NET SDK version 2.7.5 or later, or 3.5.4 or later, where the vulnerability is fixed. No other mitigations are specified. Patch status is confirmed by the vendor advisory indicating fixes in these versions.

Description

The OpenAPI.NET SDK contains a useful object model for OpenAPI documents in .NET along with common serializers to extract raw OpenAPI JSON and YAML documents from the model. From 2.0.0-preview11 until 2.7.5 and 3.5.4, a 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. This vulnerability is fixed in 2.7.5 and 3.5.4.

Impact

An attacker can cause a denial of service by supplying a crafted OpenAPI document with circular schema references, leading to a stack overflow and process termination. There is no impact on confidentiality or integrity, only availability is affected.

Summary

CVE-2026-49451 is an uncontrolled recursion vulnerability (CWE-674) in the Microsoft OpenAPI.NET SDK. When parsing OpenAPI documents containing circular schema references, the SDK's public reader APIs for both JSON and YAML can enter infinite recursion, causing a stack overflow and process crash. This affects versions starting from 2.0.0-preview11 up to but excluding 2.7.5 and 3.5.4. The vulnerability has a CVSS 3.1 base score of 7.5 (high severity) due to its network attack vector, low attack complexity, no privileges or user interaction required, and impact on availability only. The issue is resolved in versions 2.7.5 and 3.5.4.

CWE-674Uncontrolled Recursion (opens in a new tab)
Class weakness
The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.
Implementation
Ensure that an end condition will be reached under all logic conditions. The end condition may include checking against the depth of recursion and exiting with an error if the recursion goes too deep. The complexity of the end condition contributes to the effectiveness of this action.
Implementation
Increase the stack size.
Attack patterns
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/microsoft/OpenAPI.NET/security/advisories/GHSA-v5pm-xwqc-g5wc (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Jun 2026, 17:08 UTC

WeaknessesCWE-674

Technical details

References

Community reviews

Related threats