Skip to main content

Description

This issue occurs when NGINX Plus or NGINX Open Source is configured as a proxy, the proxied server name includes variables, and a Server Side Includes (SSI) or mirror directive sends a subrequest to a location that resolves the same server name. Under these conditions, a specially crafted HTTP request may cause a use-after-free condition in a worker process. An attacker may also be able to execute code if Address Space Layout Randomization (ASLR) is disabled or the attacker can bypass ASLR. Impact: An attacker could leverage this vulnerability to crash the NGINX worker process, corrupt its memory, or perform remote code execution (RCE) Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Key Findings

as of 2026-11-22
All KEV statistics→
  • Its current EPSS score (17.1%) is higher than that of 31% of CISA KEV entries.

Severity

CVSS 3.1 · CNA · Base score8.1 HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HOpen in CVSS calculator
CVSS 4.0 · CNA · CVSS-B9.2 CRITICAL
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NOpen in CVSS calculator
SSVC · CISA-ADP
Exploitationnone
Automatableno
Technical impacttotal

Remediation Timeline

BOD 26-04, US federal agencies
Publicly exposed asset
14 days
Asset not publicly exposed
Next upgrade
fix on system upgrade

If CISA adds it to the KEV catalog: 3 days and forensic triage on a publicly exposed asset, 14 days on other assets.

Deadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (not listed) and CISA's SSVC values (automatable no, technical impact total, 2026-11-18).

How the timeline is set

Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.

Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet. Forensic triage means assessing the asset to determine whether it has been compromised. Fix on system upgrade means remediating the next time the asset receives a scheduled major upgrade or rebuild.

If CISA adds the CVE to the KEV catalog, the timeline shortens.

Affected Products

ProductAffected versions
F5
NGINX Plus
37.1.0 to <37.3.0.1
37.0.0 to <37.0.8.1
R33 to <*
F5
NGINX Open Source
1.31.0 to <1.31.9
1.30.0 to <1.30.7
0.6.18 to <*

Solutions and Workarounds

from the CNA's CVE record

Workarounds

Avoid using SSI or mirror directives and avoid configuring a proxied server name with variables

References

1 links

Record Details

Published
2026-11-18
Last updated
2026-11-20
Assigner (CNA)
f5
Credited to
F5 acknowledges Xint.io for bringing this issue to our attention and following the highest standards of coordinated disclosure.

More from F5

CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.