cve.bz

CVE-2026-95101 f5: Improper Encoding or Decoding of Data

6.9 mediumEPSS 0.3%

Medium (6.9) in f5. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

6.9 medium
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

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 29th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-172 Improper Encoding or Decoding of Data
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-95101 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-95101?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-95101?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-95101 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-95101

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-95101](https://cve.bz/cve/badge/CVE-2026-95101.svg)](https://cve.bz/cve/CVE-2026-95101)

HTML:

<a href="https://cve.bz/cve/CVE-2026-95101"><img src="https://cve.bz/cve/badge/CVE-2026-95101.svg" alt="CVE-2026-95101"></a>

Affected

  • f5:nginx open source
  • f5:nginx plus

Versions

From the CNA's record in the CVE List.

ProductAffected
F5 NGINX Plusfrom 37.1.0 before 37.2.0.1
F5 NGINX Plusfrom 37.0.0 before 37.0.7.1
F5 NGINX PlusR36 and later
F5 NGINX PlusR35 and later
F5 NGINX PlusR34 and later
F5 NGINX PlusR33 and later
F5 NGINX Open Sourcefrom 1.31.0 before 1.31.7
F5 NGINX Open Sourcefrom 1.30.0 before 1.30.6
F5 NGINX Open Source1.25.0 and later

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12nginxno fix listedDEBIAN-CVE-2026-95101
Debian13nginx1.26.3-3+deb13u10DEBIAN-CVE-2026-95101
Debian14nginx1.30.4-8DEBIAN-CVE-2026-95101
Ubuntu22.04:LTSnginx1.18.0-6ubuntu14.22USN-8955-1
Ubuntu24.04:LTSnginx1.24.0-2ubuntu7.19USN-8955-1
Ubuntu26.04:LTSnginx1.28.3-2ubuntu1.12UBUNTU-CVE-2026-95101 USN-8955-1
Ubuntu26.10nginx1.30.4-7ubuntu1.1UBUNTU-CVE-2026-95101 USN-8955-1
Red Hathummingbird:1nginx, nginx-core, nginx-mod-mail and 9 more0:1.30.6-1.hum1RHSA-2026:83427
openSUSETumbleweednginx1.31.7-1.1openSUSE-SU-2026:12143-1
Alpinev3.24nginx1.30.6-r0ALPINE-CVE-2026-95101
Azure Linux3nginx1.30.6-1AZL-108449
Alpaquita23, 25, streamnginx, nginx-base1.30.6-r0BELL-CVE-2026-95101
BellSoft Hardened Containers23, 25, streamnginx-base1.30.6-r0BELL-CVE-2026-95101

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · openSUSE · Alpine · Alpaquita · BellSoft Hardened Containers.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A flaw was found in NGINX within the HTTP/3 module (ngx_http_v3_module). When HTTP/3 is configured and proxy_request_buffering is active, an unauthenticated remote attacker can inject arbitrary data into proxied client requests. An attacker can exploit this condition to manipulate request payloads forwarded to upstream backend services, compromising data integrity at the proxy layer. Default SELinux confinement (httpd_t) and unprivileged worker execution prevent privilege escalation or container escape, restricting the impact entirely to the proxied HTTP data stream.

Red Hat's mitigation

Disable HTTP/3 by removing the quic parameter from all listen directives, or configure proxy_request_buffering off; within the relevant http, server, or location blocks.

ProductPackageStateAdvisory
Red Hat Hardened Imagesnginx-main-1.30.6-1.hum1Fixed 2026-10-15RHSA-2026:83427
Red Hat Enterprise Linux 10nginxFix deferred
Red Hat Enterprise Linux 8nginx:1.24/nginxNot affected
Red Hat Enterprise Linux 9nginxNot affected
Red Hat Enterprise Linux 9nginx:1.24/nginxNot affected
Red Hat Enterprise Linux 9nginx:1.26/nginxFix deferred
Red Hat Hardened ImagesphpNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-95101.

Attack patterns (CAPEC)

  • CAPEC-3 Using Leading 'Ghost' Character Sequences to Bypass Input Filters Likelihood: Medium · Severity: Medium
  • CAPEC-52 Embedding NULL Bytes Likelihood: High · Severity: High
  • CAPEC-53 Postfix, Null Terminate, and Backslash Likelihood: High · Severity: High
  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-71 Using Unicode Encoding to Bypass Validation Logic Likelihood: Medium · Severity: High
  • CAPEC-72 URL Encoding Likelihood: High · Severity: High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-80 Using UTF-8 Encoding to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-120 Double Encoding Likelihood: Low · Severity: Medium
  • CAPEC-267 Leverage Alternate Encoding Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON