cve.bz

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

6.3 mediumEPSS 0.3%Fix available

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

On this page
When NGINX Open Source is configured to proxy HTTP/2 traffic by setting proxy_http_version to 2, and also uses proxy_set_body, an attacker may be able to inject frame headers and payload bytes to the upstream peer.  Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Severity

CVSS 4.0

6.3 medium
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N

CVSS 3.1

5.8 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 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-05-13. 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
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-42926 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-42926?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-42926?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-42926 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-42926

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-42926](https://cve.bz/cve/badge/CVE-2026-42926.svg)](https://cve.bz/cve/CVE-2026-42926)

HTML:

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

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
F5 NGINX Open Sourcefrom 1.29.4 before 1.30.1

Fixed in

ProductFixed in
F5 NGINX Open Source1.31.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14nginx1.30.0-4DEBIAN-CVE-2026-42926
Red Hathummingbird:1nginx, nginx-core, nginx-mod-mail and 9 more0:1.30.2-1.hum1RHSA-2026:20351
openSUSETumbleweednginx1.31.0-1.1openSUSE-SU-2026:10796-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Red Hat · openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A moderate severity flaw was found in NGINX Open Source, which is shipped in Red Hat Enterprise Linux 8, 9, and 10 (including the nginx:1.24 and nginx:1.26 module streams) and Red Hat In-Vehicle OS 2.0. When NGINX is configured to proxy HTTP/2 traffic by setting proxy_http_version to 2 and also uses the proxy_set_body directive, a remote attacker may be able to inject HTTP/2 frame headers and payload bytes to the upstream peer, potentially leading to unintended data manipulation or bypass of security controls. Exploitation requires this specific configuration combination, which limits exposure to deployments that use both directives together. For the affected Red Hat Enterprise Linux and Red Hat In-Vehicle OS streams, fixes are currently deferred, so no update is scheduled at this time and the residual risk remains for deployments using the affected configuration; several Red Hat Enterprise Linux streams are out of support scope and will not receive a fix. Red Hat Hardened Images and Fedora are also affected, with fixes pursued through those channels. Red Hat and upstream both rate this flaw as moderate severity (Red Hat CVSS 5.8, upstream CVSS 6.3).

Red Hat's mitigation

To mitigate this issue, avoid configuring NGINX to proxy HTTP/2 traffic with the `proxy_http_version 2` directive in conjunction with `proxy_set_body`. If HTTP/2 proxying is essential, ensure that all proxied content is thoroughly validated to prevent malicious data injection. Modifying NGINX configuration files typically requires a service reload or restart for changes to take effect.

ProductPackageStateAdvisory
Red Hat Hardened Imagesnginx-main-1.30.2-1.hum1Fixed 2026-05-23RHSA-2026:20351
Red Hat Enterprise Linux 10nginxFix deferred
Red Hat Enterprise Linux 8nginx:1.24/nginxFix deferred
Red Hat Enterprise Linux 9nginxFix deferred
Red Hat Enterprise Linux 9nginx:1.24/nginxFix deferred
Red Hat Enterprise Linux 9nginx:1.26/nginxFix deferred

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-42926.

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