CVE-2026-95101VulnerabilityPublished 17 Oct 2026Updated 2 Nov 2026

Microsoft · NGINX ngx_http_v3_module vulnerability

Affects MicrosoftSource GCVE Database

Compare

Authoritative record:CVE-2026-95101· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium · fixed in 37.2.0.1 : update Microsoft when convenient.

Data as of 2 Nov 2026, 10:58 UTC

CVSS 3.1 base score

5.3Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 37.2.0.1, 37.0.7.1, 1.31.7 +1

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

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

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: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Oct 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 2 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.

microsoft-security-response-ce

What to do

Upgrade NGINX Plus to 37.2.0.1 or 37.0.7.1; NGINX Open Source to 1.31.7 or 1.30.6; f5/nginx-plus to 37.2.0.1, 37.0.7.1, 1.31.7 or 1.30.6.

Affected software

Product	Affected	Fixed in
F5NGINX Plus	Affected >=37.1.0 <37.2.0.1 >=37.0.0 <37.0.7.1 >=R36 >=R35 >=R34 >=R33	Fixed in 37.2.0.1 37.0.7.1
F5NGINX Open Source	Affected >=1.31.0 <1.31.7 >=1.30.0 <1.30.6 >=1.25.0	Fixed in 1.31.7 1.30.6
F5f5/nginx-plus`pkg:rpm/f5/nginx-plus`Other threats	Affected >=37.1.0 <37.2.0.1 >=37.0.0 <37.0.7.1 >=36 >=35 >=34 >=33 >=1.31.0 <1.31.7 >=1.30.0 <1.30.6 >=1.25.0	Fixed in 37.2.0.1 37.0.7.1 1.31.7 1.30.6

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

Description

CVE-2026-95101 is a published vulnerability affecting version 3.0 of the NGINX ngx_http_v3_module. The vulnerability is cataloged under CWE-172. There is no evidence of exploitation in the wild.

CWE-172Improper Encoding or Decoding of Data (opens in a new tab)
Class weakness
The product does not properly encode or decode data, resulting in unexpected values that are not equivalent to the original data.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Implementation · Output Encoding
While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments.
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
Attack patterns
Double Encoding (opens in a new tab)
Leverage Alternate Encoding (opens in a new tab)
Using Leading 'Ghost' Character Sequences to Bypass Input Filters (opens in a new tab)
Embedding NULL Bytes (opens in a new tab)
Postfix, Null Terminate, and Backslash (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

WeaknessesCWE-172

Technical details

References

Community reviews

Related threats