Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-42055: NGINX Plus and NGINX Open Source have a vulnerability in the ngx_http_proxy_v2_module and ngx_http_grpc_module

62
This week
HIGH 8.1REMOTEWATCHLISTUPGRADEUPGRADEUPGRADE

CVE-2026-42055 is a high-severity flaw (CVSS 8.1) affecting dos, nginx gateway fabric, nginx ingress controller. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

NGINX Plus and NGINX Open Source have a vulnerability in the ngx_http_proxy_v2_module and ngx_http_grpc_module modules. This vulnerability exists when the proxy_http_version to 2 or grpc_pass directives are used to proxy HTTP/2 traffic, the ignore_invalid_headers directive is set to off, and the large_client_header_buffers directive size is larger than 2 megabytes. A remote, unauthenticated attacker, along with conditions beyond their control, co

Why this priority

  • High severity
  • EPSS top 6%: very likely to be exploited
  • Remotely exploitable, no login, no user action
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score8.1 (High)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededNone
User interactionNone
EPSS exploit chance6.5% (top 6%)
CISA exploited listNo
WeaknessCWE-122, CWE-787, CWE-131
Published2026-06-17
Last modified2026-09-14
Publisher (CNA): F5 Networks · Vendor: f5

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

f5 dos UPGRADE
Affected: >= 4.3.0 and <= 4.7.0 · 4.9.0
Fixed in: newer than 4.7.0
Safe to downgrade to: a release before 4.3.0
1. Check installed version
apt-cache policy dos || rpm -q dos || dos --version
2. UPGRADE to newer than 4.7.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade dos
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade dos
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 4.3.0 (Debian / Ubuntu)
apt-cache madison dos sudo apt install dos=<VERSION_BEFORE_4.3.0> sudo apt-mark hold dos
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list dos sudo dnf downgrade dos-<VERSION_BEFORE_4.3.0> sudo dnf versionlock add dos
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 gateway fabric UPGRADE
Affected: >= 1.3.0 and <= 1.6.2 · >= 2.0.0 and <= 2.6.3
Fixed in: newer than 2.6.3
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.3 (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 ingress controller UPGRADE
Affected: >= 3.5.0 and <= 3.7.2 · >= 4.0.0 and <= 4.0.1 · >= 5.0.0 and <= 5.5.0
Fixed in: newer than 5.5.0
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.5.0 (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.
f5 nginx instance manager UPGRADE
Affected: >= 2.17.0 and <= 2.22.0
Fixed in: newer than 2.22.0
Safe to downgrade to: a release before 2.17.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.17.0 (Debian / Ubuntu)
apt-cache madison nginx-instance-manager sudo apt install nginx-instance-manager=<VERSION_BEFORE_2.17.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.17.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 open source UPGRADE
Affected: >= 1.0.0 and <= 1.30.2 · >= 1.31.0 and <= 1.31.1
Fixed in: newer than 1.31.1
Safe to downgrade to: a release before 1.0.0
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.31.1 (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.0.0 (Debian / Ubuntu)
apt-cache madison nginx-open-source sudo apt install nginx-open-source=<VERSION_BEFORE_1.0.0> 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.0.0> 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 plus UPGRADE
Affected: >= 37.0.0.1 and < 37.0.2.1 · >= r33 and < r36 · r36 · r36 p1 · r36 p2 · r36 p3 · r36 p4 · r36 p5
Fixed in: 37.0.2.1, r36
Safe to downgrade to: a release before 37.0.0.1
1. Check installed version
apt-cache policy nginx-plus || rpm -q nginx-plus || nginx-plus --version
2. UPGRADE to 37.0.2.1 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade nginx-plus
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade nginx-plus
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 37.0.0.1 (Debian / Ubuntu)
apt-cache madison nginx-plus sudo apt install nginx-plus=<VERSION_BEFORE_37.0.0.1> sudo apt-mark hold nginx-plus
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list nginx-plus sudo dnf downgrade nginx-plus-<VERSION_BEFORE_37.0.0.1> sudo dnf versionlock add nginx-plus
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.

Exact fixes by distribution

Fedora 46 · ruff · FIXED · 0.17.3-1.fc46 · FEDORA-2026-63898fdcbb · source
sudo dnf upgrade --advisory=FEDORA-2026-63898fdcbb
Fedora ELN · xorg-x11-server-Xwayland · FIXED · 26.0.99.903-2.eln159 · FEDORA-2026-4581dab0ed · source
sudo dnf upgrade --advisory=FEDORA-2026-4581dab0ed
Ubuntu 22.04 · nginx · FIXED · 1.18.0-6ubuntu14.16
sudo apt update && sudo apt install --only-upgrade nginx dpkg --compare-versions "$(dpkg-query -W -f='${Version}' nginx)" ge "1.18.0-6ubuntu14.16" && echo PATCHED || echo STILL-VULNERABLE
Ubuntu 24.04 · nginx · FIXED · 1.24.0-2ubuntu7.13
sudo apt update && sudo apt install --only-upgrade nginx dpkg --compare-versions "$(dpkg-query -W -f='${Version}' nginx)" ge "1.24.0-2ubuntu7.13" && echo PATCHED || echo STILL-VULNERABLE
Ubuntu 25.10 · nginx · FIXED · 1.28.0-6ubuntu1.8
sudo apt update && sudo apt install --only-upgrade nginx dpkg --compare-versions "$(dpkg-query -W -f='${Version}' nginx)" ge "1.28.0-6ubuntu1.8" && echo PATCHED || echo STILL-VULNERABLE
Debian 12 · nginx · FIXED · 1.22.1-9+deb12u9
sudo apt update && sudo apt install --only-upgrade nginx dpkg --compare-versions "$(dpkg-query -W -f='${Version}' nginx)" ge "1.22.1-9+deb12u9" && echo PATCHED || echo STILL-VULNERABLE
Debian 13 · nginx · FIXED · 1.26.3-3+deb13u7
sudo apt update && sudo apt install --only-upgrade nginx dpkg --compare-versions "$(dpkg-query -W -f='${Version}' nginx)" ge "1.26.3-3+deb13u7" && echo PATCHED || echo STILL-VULNERABLE
RHEL 10 · nginx · FIXED · nginx-1.26.3-6.el10_2.5
sudo dnf upgrade --advisory=RHSA-2026:36364 rpm -q nginx
RHEL 9 · nginx · FIXED · nginx-1.20.1-28.el9_8.4
sudo dnf upgrade --advisory=RHSA-2026:36331 rpm -q nginx
Alpine 3.21 · nginx · FIXED · nginx-1.26.3-r2
apk add --upgrade nginx apk info -v nginx
Alpine 3.22 · nginx · FIXED · nginx-1.28.3-r4
apk add --upgrade nginx apk info -v nginx
Alpine 3.23 · nginx · FIXED · nginx-1.28.3-r4
apk add --upgrade nginx apk info -v nginx
Alpine 3.24 · nginx · FIXED · nginx-1.30.3-r0
apk add --upgrade nginx apk info -v nginx
Amazon Linux 2023 · see advisory · FIXED · ALAS2023-2026-1922 · source
sudo dnf update --advisory=ALAS2023-2026-1922

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Advisories and coverage

Official advisories

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-42055?

dos: upgrade to newer than 4.7.0; nginx gateway fabric: upgrade to newer than 2.6.3; nginx ingress controller: upgrade to newer than 5.5.0. Exact commands for each OS are on this page.

Is CVE-2026-42055 being exploited?

CVE-2026-42055 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-42055 affect?

CVE-2026-42055 affects dos, nginx gateway fabric, nginx ingress controller. Severity is high (CVSS 8.1). NGINX Plus and NGINX Open Source have a vulnerability in the ngx_http_proxy_v2_module and ngx_http_grpc_module modules. This vulnerability exists when the proxy_http_version to 2 or grpc_pass directives are used to proxy HTTP/2 traffic, the

How urgent is CVE-2026-42055?

Priority 62/100. High severity; EPSS top 6%: very likely to be exploited; 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.