CVE-2026-93479: NGINX map directive and regex matching vulnerability
Noroxi assessment
Priority: Monitor (action score 36/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.1% (FIRST EPSS); higher than 68.1% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: azl3 nginx 1.30.4-1 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to azl3 nginx 1.30.4-1 on Azure Linux 3.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A vulnerability exists in NGINX Plus and NGINX Open Source when a map directive uses regex matching and the root directive or access log format references the map's regex capture variables before referencing the map output variable. Alternatively, the same result could be achieved by using a non-cacheable variable in a string expression under certain conditions. An unauthenticated attacker along with conditions beyond their control can exploit this vulnerability by sending crafted HTTP requests. This may cause a heap buffer overflow in the NGINX worker process leading to a restart. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR. Impact: This vulnerability may allow remote attackers to cause a denial-of-service (DoS) on the NGINX system or to possibly trigger a code execution. There is no control plane exposure; this is a data plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
- Published
- Oct 14, 2026
- Updated
- Oct 29, 2026
- EPSS
- 1.1% · 68th percentile
- CWE
- CWE-122
Report tools
Action score
36
Monitor
Low priority for now.
- CVSS
- 36 / 40 · 9.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · f5
- 8.1
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Using nginx plus? Add it to your stack and be the first to know about CVEs like this one. (Nginx)
Is nginx on your server exposed to the internet?
The free port scanner finds the open ports on your server and matches the service versions it can read against known vulnerabilities. No account needed.
Run a port scanVersions reported by the vendor
Affected version ranges reported by the assigning authority (f5). Independent of NVD's CPE analysis and usually ahead of it.
F5 NGINX Open Source
- 1.31.2 and later · before 1.31.7affected
- 1.30.0 and later · before 1.30.6affected
F5 NGINX Plus
- 37.1.0 and later · before 37.1.0.1affected
- 37.0.0 and later · before 37.0.5.1affected
- R36 and lateraffected
- R35 and lateraffected
- R34 and lateraffected
- R33 and lateraffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.24 | nginx | before 1.30.6-r0 | 1.30.6-r0 |
| Debian:12 | nginx | from 0 | — |
| Debian:13 | nginx | before 1.26.3-3+deb13u10 | 1.26.3-3+deb13u10 |
| Debian:14 | nginx | before 1.30.4-8 | 1.30.4-8 |
| openSUSE:Tumbleweed | nginx | before 1.31.7-1.1 | 1.31.7-1.1 |
Same product
f5: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-27654NGINX ngx_http_dav_module vulnerability43Plan
- CVE-2026-97205NGINX ngx_http_core_module vulnerability36Monitor
- CVE-2026-15176NGINX ngx_http_core_module vulnerability36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-32647Mar 24, 2026 · NGINX ngx_http_mp4_module vulnerability34Monitor
- ← EarlierCVE-2026-90439Sep 15, 2026 · NGINX ngx_http_v3_module vulnerability27Monitor
- Later →CVE-2026-95101Oct 14, 2026 · NGINX ngx_http_v3_module vulnerability27Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| azl3 nginx 1.30.4-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| alpine:nginx | 1.30.6-r0 · Alpine:v3.24 | Package registry (OSV) |
| debian:nginx | 1.26.3-3+deb13u10 · Debian:13 | Package registry (OSV) |
| debian:nginx | 1.30.4-8 · Debian:14 | Package registry (OSV) |
| opensuse:nginx | 1.31.7-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recorded+3 d
- TodayNov 1, 2026+18 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-27654204 days apartNGINX ngx_http_dav_module vulnerability43Plan
- CVE-2026-151760 days apartNGINX ngx_http_core_module vulnerability36Monitor
- CVE-2026-9043929 days apartNGINX ngx_http_v3_module vulnerability27Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-122 · Heap-based Buffer OverflowCVSS vector
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
- SSVC exploitation— → none
- Exploit maturity— → none
- CVSS8.1 → 9.2
- Severityhigh → critical
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.