CVE-2026-123007 in the critical feed json
NGINX ngx_http_v2_module vulnerability
published 10h ago modified 4h ago also EUVD-2026-128949
- cvss
- 9.2
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
This issue affects NGINX Plus or NGINX Open Source configurations that use HTTP/2. When NGINX processes undisclosed traffic, the flow control window can exceed the allowed threshold, potentially resulting in a heap buffer overflow typically followed by an NGINX worker segmentation fault. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR.
Impact: An attacker could leverage this vulnerability to crash the NGINX worker process, corrupt its memory, or potentially execute code remotely. 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.
Patch / fix
- F5 NGINX Plus 37.0.8.1, 37.3.0.1
- F5 NGINX Open Source 1.30.7, 1.31.9
- nginx AlmaLinux 10 2:1.26.3-16.el10_3.1.alma.2
- nginx-core AlmaLinux 10 2:1.26.3-16.el10_3.1.alma.2
- nginx-mod-mail AlmaLinux 10 2:1.26.3-16.el10_3.1.alma.2
- nginx-filesystem AlmaLinux 10 2:1.26.3-16.el10_3.1.alma.2
- nginx-mod-stream AlmaLinux 10 2:1.26.3-16.el10_3.1.alma.2
- nginx-all-modules AlmaLinux 10 2:1.26.3-16.el10_3.1.alma.2
- nginx-mod-http-perl AlmaLinux 10 2:1.26.3-16.el10_3.1.alma.2
- nginx-mod-http-xslt-filter AlmaLinux 10 2:1.26.3-16.el10_3.1.alma.2
almalinux advisories ALSA-2026:A024ALSA-2026:A025
- github.com/nginx/nginx@b89c410 commit
- github.com/chainguard-forks/ingress-nginx#69 pull request
- my.f5.com/manage/s/article/K000163926 advisory
Is CVE-2026-123007 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-123007 updated cvss 8.1
nginx: NGINX flow control window overflow in HTTP/2
-
Red Hat Enterprise Linux 8 nginx, nginx-mod-mail, nginx-filesystem, nginx-mod-stream, nginx-all-modules, nginx-mod-http-perl, +2 more Red Hat Enterprise Linux 9 nginx, nginx-core, nginx-mod-mail, nginx-filesystem, nginx-mod-stream, nginx-all-modules, +3 more Red Hat Enterprise Linux 10 nginx Red Hat Hardened Images nginxaffected: workaround, no fix available
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 10h ago
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 4.0 | 9.2 | CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
Affected products
- F5 NGINX Plus
- F5 NGINX Open Source
Classification
- Weakness
- Technology feeds
References
-
my.f5.com
/manage/s/article/K000163926
vendor-advisory, patch
- github.com /nginx/nginx/commit/b89c4100bf6762a45e4a6463eaf4b70368277c94
- github.com /chainguard-forks/ingress-nginx/pull/69
- wiz.io /blog/nginx-http2-rce-vulnerabilities
- news.ycombinator.com /item?id=50547374
- ubuntu.com /security/CVE-2026-123007
- github.com /advisories/GHSA-m4q8-cf44-f42r
- github.com /openresty/openresty/issues/1165
- github.com /nginx/nginx/issues/2002
- nginx.org /en/CHANGES
- cyberscoop.com /nginx-critical-vulnerabilities-exploits/
- rapid7.com /blog/post/ve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed/
- xint.io /blog/nginx2root-remote-code-execution
- nginx2root.com
- access.redhat.com /security/cve/cve-2026-123007
Sources
- CVE List CVE-2026-123007
- NVD CVE-2026-123007
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.