Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-42926: When NGINX Open Source is configured to proxy HTTP/2 traffic by setting proxy_http_version to 2, and also uses

37
Routine
MEDIUM 5.8REMOTEWATCHLISTUPGRADEUPGRADEUPGRADE

CVE-2026-42926 is a medium-severity flaw (CVSS 5.8) affecting nginx gateway fabric, nginx open source, nginx instance manager. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • Remotely exploitable, no login, no user action
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score5.8 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.3% (top 72%)
CISA exploited listNo
WeaknessCWE-172
Published2026-05-13
Last modified2026-10-26
Publisher (CNA): F5 Networks · Vendor: f5

Share: LinkedIn · X · Reddit

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

f5 nginx gateway fabric UPGRADE
Affected: >= 1.3.0 and <= 1.6.2 · >= 2.0.0 and <= 2.6.0
Fixed in: newer than 2.6.0
Safe to downgrade to: a release before 1.3.0
1. Check installed version
apt-cache policy nginx-gateway-fabric || rpm -q nginx-gateway-fabric || nginx-gateway-fabric --version
2. UPGRADE to newer than 2.6.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade nginx-gateway-fabric
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade nginx-gateway-fabric
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 1.3.0 (Debian / Ubuntu)
apt-cache madison nginx-gateway-fabric sudo apt install nginx-gateway-fabric=<VERSION_BEFORE_1.3.0> sudo apt-mark hold nginx-gateway-fabric
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list nginx-gateway-fabric sudo dnf downgrade nginx-gateway-fabric-<VERSION_BEFORE_1.3.0> sudo dnf versionlock add nginx-gateway-fabric
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
f5 nginx open source UPGRADE
Affected: >= 1.29.4 and <= 1.30.0
Fixed in: newer than 1.30.0
Safe to downgrade to: a release before 1.29.4
1. Check installed version
apt-cache policy nginx-open-source || rpm -q nginx-open-source || nginx-open-source --version
2. UPGRADE to newer than 1.30.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade nginx-open-source
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade nginx-open-source
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 1.29.4 (Debian / Ubuntu)
apt-cache madison nginx-open-source sudo apt install nginx-open-source=<VERSION_BEFORE_1.29.4> sudo apt-mark hold nginx-open-source
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list nginx-open-source sudo dnf downgrade nginx-open-source-<VERSION_BEFORE_1.29.4> sudo dnf versionlock add nginx-open-source
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
f5 nginx instance manager UPGRADE
Affected: >= 2.16.0 and <= 2.22.0
Fixed in: newer than 2.22.0
Safe to downgrade to: a release before 2.16.0
1. Check installed version
apt-cache policy nginx-instance-manager || rpm -q nginx-instance-manager || nginx-instance-manager --version
2. UPGRADE to newer than 2.22.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade nginx-instance-manager
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade nginx-instance-manager
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 2.16.0 (Debian / Ubuntu)
apt-cache madison nginx-instance-manager sudo apt install nginx-instance-manager=<VERSION_BEFORE_2.16.0> sudo apt-mark hold nginx-instance-manager
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list nginx-instance-manager sudo dnf downgrade nginx-instance-manager-<VERSION_BEFORE_2.16.0> sudo dnf versionlock add nginx-instance-manager
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
f5 nginx ingress controller UPGRADE
Affected: >= 3.5.0 and <= 3.7.2 · >= 4.0.0 and <= 4.0.1 · >= 5.0.0 and <= 5.4.2
Fixed in: newer than 5.4.2
Safe to downgrade to: a release before 3.5.0
1. Check installed version
apt-cache policy nginx-ingress-controller || rpm -q nginx-ingress-controller || nginx-ingress-controller --version
2. UPGRADE to newer than 5.4.2 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade nginx-ingress-controller
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade nginx-ingress-controller
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 3.5.0 (Debian / Ubuntu)
apt-cache madison nginx-ingress-controller sudo apt install nginx-ingress-controller=<VERSION_BEFORE_3.5.0> sudo apt-mark hold nginx-ingress-controller
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list nginx-ingress-controller sudo dnf downgrade nginx-ingress-controller-<VERSION_BEFORE_3.5.0> sudo dnf versionlock add nginx-ingress-controller
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-42926?

nginx gateway fabric: upgrade to newer than 2.6.0; nginx open source: upgrade to newer than 1.30.0; nginx instance manager: upgrade to newer than 2.22.0. Exact commands for each OS are on this page.

Is CVE-2026-42926 being exploited?

CVE-2026-42926 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-42926 affect?

CVE-2026-42926 affects nginx gateway fabric, nginx open source, nginx instance manager. Severity is medium (CVSS 5.8). 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

How urgent is CVE-2026-42926?

Priority 37/100. Remotely exploitable, no login, no user action; On your watchlist

Software pages

nginx vulnerabilities · F5 BIG-IP vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.