# CVE-2026-93479: NGINX map directive and regex matching vulnerability

> Remote attackers can cause denial of service or execute code via heap buffer overflow in NGINX when specific map directive configurations are used.

- **Severity:** Critical 9.2 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** ALPINE-CVE-2026-93479, AZL-108461, BELL-CVE-2026-93479, BIT-nginx-2026-93479, BIT-nginx-gateway-2026-93479, DEBIAN-CVE-2026-93479, ECHO-85e8-7da2-8a29, GHSA-v72q-v4vf-2mx7, ROOT-OS-DEBIAN-12-CVE-2026-93479, UBUNTU-CVE-2026-93479

## What is CVE-2026-93479?

CVE-2026-93479 is a critical memory corruption vulnerability in F5 NGINX Open Source, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2026-93479?

2 open source packages ship an affected version, including nginx and nginx-gateway.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nginx` | Bitnami | From 1.30.0 | 1.30.6, 1.31.7 |
| `nginx-gateway` | Bitnami | From 1.30.0 | 1.30.6, 1.31.7 |

## How do I fix CVE-2026-93479?

Upgrade nginx to a fixed version for your release line: 1.30.6 or 1.31.7.

## Is CVE-2026-93479 being exploited?

There is no known exploitation of CVE-2026-93479 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93479 and fix it if it is affected.

What it is: CVE-2026-93479 is a critical memory corruption vulnerability in F5 NGINX Open Source, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93479 in the wild and no public exploit code.

Affected packages and fixed versions:
- nginx (Bitnami): affected from 1.30.0; fixed in 1.30.6, 1.31.7
- nginx-gateway (Bitnami): affected from 1.30.0; fixed in 1.30.6, 1.31.7

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93479/ (Markdown: https://insights.sbomify.com/CVE-2026-93479/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93479
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93479
- OSV: https://osv.dev/vulnerability/CVE-2026-93479

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93479/
Summaries are generated and may contain mistakes; the official description above is the record.