# CVE-2026-95101: NGINX ngx_http_v3_module vulnerability

> An unauthenticated attacker can inject data into proxied requests when HTTP/3 and proxy_request_buffering are enabled in NGINX.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/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:** 15 Oct 2026
- **Also known as:** ALPINE-CVE-2026-95101, AZL-108449, BELL-CVE-2026-95101, BIT-nginx-2026-95101, BIT-nginx-gateway-2026-95101, DEBIAN-CVE-2026-95101, ECHO-b17b-3f9b-fc08, GHSA-g6r5-95cx-mpp9, UBUNTU-CVE-2026-95101

## What is CVE-2026-95101?

CVE-2026-95101 is a medium-severity 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

Description
NGINX Plus and NGINX Open Source have a vulnerability in the ngx_http_v3_module module. When using HTTP/3 with 

proxy_request_buffering on directive, an unauthenticated attacker may be able to inject data in the proxied request.

Impact

This vulnerability may allow remote attackers to 

inject data in the proxied request.  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-172 (Improper Encoding or Decoding of Data)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nginx` | Bitnami | From 1.25.0 | 1.29.0, 1.30.6, 1.31.7 |
| `nginx-gateway` | Bitnami | From 1.25.0 | 2.2.1 |

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

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

## Is CVE-2026-95101 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-95101 is a medium-severity 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-95101 in the wild and no public exploit code.

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

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-95101/ (Markdown: https://insights.sbomify.com/CVE-2026-95101/index.md)
```

## Sources

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

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