NVD / CVE Program· CNA f5

CVE-2026-42926: NGINX ngx_http_proxy_v2_module vulnerability

Noroxi assessment

Priority: Monitor (action score 25/100)

Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 0.34% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: F5 NGINX Open Source 1.30.1.

Low priority for now. Upgrade to F5 NGINX Open Source 1.30.1 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

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.

MediumCVSS 6.3 · v4.0—Proof of concept Fix available

Pre-auth

Published: May 13, 2026
Updated: Oct 26, 2026
EPSS: 0.3% · 28th percentile
CWE: CWE-172

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 25 / 40 · 6.3 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · f5: 5.8; NVD has not scored this yet; the score shown is the CNA’s.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N

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
Proof of concept exists, no weaponized module
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

Is your version affected? Check it

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 help

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

Vendor	Product	CPE
f5	nginx gateway fabric	cpe:2.3:a:f5:nginx_gateway_fabric
f5	nginx open source	cpe:2.3:a:f5:nginx_open_source
f5	nginx instance manager	cpe:2.3:a:f5:nginx_instance_manager
f5	nginx ingress controller	cpe:2.3:a:f5:nginx_ingress_controller

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

f5 nginx gateway fabric2.0.0 and later · up to 2.6.0 inclusive
f5 nginx gateway fabric1.3.0 and later · up to 1.6.2 inclusive
f5 nginx ingress controller4.0.0 and later · up to 4.0.1 inclusive
f5 nginx ingress controller5.0.0 and later · up to 5.4.2 inclusive
f5 nginx ingress controller3.5.0 and later · up to 3.7.2 inclusive
f5 nginx instance manager2.16.0 and later · up to 2.22.0 inclusive
f5 nginx open source1.29.4 and later · up to 1.30.0 inclusive

Versions 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.0 and laternot affected · semver
- 1.29.4 and later · before 1.30.1affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:14	nginx	before 1.30.0-4	1.30.0-4
openSUSE:Tumbleweed	nginx	before 1.31.0-1.1	1.31.0-1.1
Red Hat:hummingbird:1	nginx	before 0:1.30.2-1.hum1	0:1.30.2-1.hum1
Red Hat:hummingbird:1	nginx-all-modules	before 0:1.30.2-1.hum1	0:1.30.2-1.hum1
Red Hat:hummingbird:1	nginx-core	before 0:1.30.2-1.hum1	0:1.30.2-1.hum1
Red Hat:hummingbird:1	nginx-filesystem	before 0:1.30.2-1.hum1	0:1.30.2-1.hum1
Red Hat:hummingbird:1	nginx-mod-devel	before 0:1.30.2-1.hum1	0:1.30.2-1.hum1
Red Hat:hummingbird:1	nginx-mod-http-geoip	before 0:1.30.2-1.hum1	0:1.30.2-1.hum1
Red Hat:hummingbird:1	nginx-mod-http-image-filter	before 0:1.30.2-1.hum1	0:1.30.2-1.hum1
Red Hat:hummingbird:1	nginx-mod-http-perl	before 0:1.30.2-1.hum1	0:1.30.2-1.hum1
Red Hat:hummingbird:1	nginx-mod-http-xslt-filter	before 0:1.30.2-1.hum1	0:1.30.2-1.hum1
Red Hat:hummingbird:1	nginx-mod-mail	before 0:1.30.2-1.hum1	0:1.30.2-1.hum1
Red Hat:hummingbird:1	nginx-mod-stream	before 0:1.30.2-1.hum1	0:1.30.2-1.hum1
Red Hat:hummingbird:1	nginx-mod-stream-geoip	before 0:1.30.2-1.hum1	0:1.30.2-1.hum1

Same product

f5: all records

Other highest-scoring records for the same primary product.

CVE-2026-42533NGINX Map directive and Regex matching vulnerability
38Monitor
CVE-2026-42530NGINX Open-Source ngx_http_v3_module vulnerability
38Monitor
CVE-2026-60005NGINX ngx_http_slice_module vulnerability
35Monitor

Published before and after this one in the same product

← EarlierCVE-2026-1642Feb 4, 2026 · A vulnerability exists in NGINX OSS and NGINX Plus when configured to proxy to upstream Transport Layer Security (TLS) servers.
32Monitor
Later →CVE-2026-11311Jun 17, 2026 · NGINX Gateway Fabric vulnerability
34Monitor
Later →CVE-2026-32682Jun 17, 2026 · NGINX Gateway Fabric vulnerability
28Monitor

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
F5 NGINX Open Source	1.30.1	Vendor (CNA)
alpine:nginx	0 · Alpine:v3.24	Package registry (OSV)
debian:nginx	1.30.0-4 · Debian:14	Package registry (OSV)
opensuse:nginx	1.31.0-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
red hat:nginx	0:1.30.2-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:nginx-all-modules	0:1.30.2-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:nginx-core	0:1.30.2-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:nginx-filesystem	0:1.30.2-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:nginx-mod-devel	0:1.30.2-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:nginx-mod-http-geoip	0:1.30.2-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:nginx-mod-http-image-filter	0:1.30.2-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:nginx-mod-http-perl	0:1.30.2-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:nginx-mod-http-xslt-filter	0:1.30.2-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:nginx-mod-mail	0:1.30.2-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:nginx-mod-stream	0:1.30.2-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:nginx-mod-stream-geoip	0:1.30.2-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Proof-of-concept repository on GitHub	stars:0	2026-06-06

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.

PublishedMay 13, 2026
First PoCJun 6, 2026+23 d
TodayNov 7, 2026+178 d

No history yet (it accumulates with the daily EPSS job).

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 researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

F5 acknowledges Mufeed VHWinfunc Research, Hcamael of aipyaipy, and 章鱼哥reporter

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

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.
No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: X

Weakness class (CWE)

CWE-172 · Encoding Error

CVSS vector

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/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

Obfuscated Files or InformationT1027

Change log

Fix✗ → ✓Sep 28, 2026, 10:10 PM UTC

For records you follow, these changes also arrive as notifications. →

References

my.f5.com/manage/s/article/K000161131

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records