CVE-2026-123633: When NGINX Plus or NGINX Open Source is configured to use HTTP/2 for client connections and proxy client requests to a backend, a specially crafted request can result in use-after-free in the...

High CVSS 8.1

CVE id
CVE-2026-123633
Published
Last modified

Affected packages

PackageAffected versionsFixed in
NGINX
Runtimes and servers
>= 1.19.7, < 1.30.7
>= 1.31.0, < 1.31.9
1.30.7, 1.31.9
NGINX App Protect WAF
Runtimes and servers
>= 4.12.0, <= 4.16.0
>= 5.4.0, <= 5.8.0
>= 5.9.0, < 5.16.2
5.16.2
NGINX Gateway Fabric
Runtimes and servers
>= 1.5.0, <= 1.6.2
>= 2.0.0, < 2.9.0
2.9.0
F5 NGINX Ingress Controller
Runtimes and servers
>= 5.0.0, < 5.8.0 5.8.0
NGINX Plus
Runtimes and servers
>= 37.0.0, < 37.0.7.1
>= 37.1.0, < 37.2.0.1
>= 34, < 35
>= 35, < 36
>= 36, < 37
35, 36, 37, 37.0.7.1, 37.2.0.1

Versions we track that it affects: NGINX *, NGINX 1.28.*;

How to fix it

NGINX (Runtimes and servers)

Upgrade NGINX to the fixed release of the line you run: 1.30.7, 1.31.9.

nginx -v
  • Install the patched NGINX release of your branch (the nginx image tag, the nginx.org packages, or your distribution's security update) and restart NGINX; with OpenResty, upgrade to the OpenResty release built on it.

NGINX App Protect WAF (Runtimes and servers)

Upgrade NGINX App Protect WAF to 5.16.2 or later.

  • Upgrade NGINX App Protect WAF (the app-protect packages, or the waf-enforcer and waf-config-mgr images) to the patched release.

NGINX Gateway Fabric (Runtimes and servers)

Upgrade NGINX Gateway Fabric to 2.9.0 or later.

kubectl get deploy -A -l app.kubernetes.io/name=nginx-gateway-fabric -o jsonpath='{..image}'
  • Upgrade NGINX Gateway Fabric (its Helm chart or the nginx-gateway-fabric images) to the patched release.

F5 NGINX Ingress Controller (Runtimes and servers)

Upgrade F5 NGINX Ingress Controller to 5.8.0 or later.

kubectl get deploy -A -l app.kubernetes.io/name=nginx-ingress -o jsonpath='{..image}'
  • Upgrade the NGINX Ingress Controller image (nginx/nginx-ingress or nginx-plus-ingress) or its Helm chart to the patched release and roll it out to every cluster.

NGINX Plus (Runtimes and servers)

Upgrade NGINX Plus to the fixed release of the line you run: 35, 36, 37, 37.0.7.1, 37.2.0.1.

nginx -v
  • Upgrade NGINX Plus to the patched release from the F5 repository (or your nginx-plus image) and restart it.

A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.

Details

When NGINX Plus or NGINX Open Source is configured to use HTTP/2 for client connections and proxy client requests to a backend, a specially crafted request can result in use-after-free in the worker process, if this process is running low on worker_connections. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR.

Impact:

This vulnerability may allow remote attackers to cause a denial-of-service (DoS) on the NGINX system or may allow a code execution. 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.

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.