CVE-2026-123007: NGINX ngx_http_v2_module vulnerability

Published Nov 18, 2026
·
Updated

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.

Affected Software

19 affected componentsFixes available
Nginx NGINX Plus
Nginx NGINX Open Source
F5 NGINX Plus>=37.1.0<=37.2.0.1, >=37.0.0<=37.0.7.1
37.3.0.137.0.8.1
F5 NGINX Plus=34
F5 NGINX Open Source>=1.31.0<=1.31.8, >=1.9.5<=1.30.6
1.31.91.30.7
debian/nginx*
debian/nginx*
debian/nginx*
debian/nginx<=1.22.1-9+deb12u9, <=1.22.1-9+deb12u10, <=1.26.3-3+deb13u7, <=1.26.3-3+deb13u10, <=1.30.6-3
ubuntu/nginx*
ubuntu/nginx*
ubuntu/nginx*
ubuntu/nginx*
ubuntu/nginx*
ubuntu/nginx*
ubuntu/nginx*
alpine/nginx<1.28.3-r8
1.28.3-r8
alpine/nginx<1.28.3-r8
1.28.3-r8
alpine/nginx<1.30.7-r0
1.30.7-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 37.3.0.1Fixed in 37.0.8.1
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.31.9Fixed in 1.30.7
  3. Upgrade

    Upgrade alpine/nginx to a version that resolves this vulnerability.

    Fixed in 1.28.3-r8
  4. Upgrade

    Upgrade alpine/nginx to a version that resolves this vulnerability.

    Fixed in 1.30.7-r0

Event History

Nov 18, 2026
Advisory Published
via F5·02:49 PM
Data Sourced
via F5·02:49 PM
DescriptionSeverityWeaknessAffected Software
CVE Published
via OSV·03:23 PM
Data Sourced
via OSV·03:23 PM
DescriptionSeverityAffected Software
CVE Published
via MITRE·03:23 PM
Data Sourced
via MITRE·03:23 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:18 PM
DescriptionSeverityWeakness
News Published
via The Register·09:11 PM

Frequently Asked Questions

1

Which deployments are exposed to this issue?

NGINX Plus and NGINX Open Source deployments that use HTTP/2 are affected. The issue is in data-plane traffic handling and does not expose the control plane.

2

What access does an attacker need?

The vector is network-based and requires no privileges or user interaction. Exploitation requires processing specially crafted, undisclosed traffic that causes the HTTP/2 flow-control window to exceed its allowed threshold.

3

What is the likely impact if exploitation succeeds?

The typical result is an NGINX worker segmentation fault, which can disrupt service. The overflow can also corrupt memory; remote code execution may be possible where ASLR is disabled or can be bypassed.

4

How can I tell whether my deployment may be affected?

Determine whether the NGINX instance accepts or processes HTTP/2 traffic. Software versions that have reached End of Technical Support were not evaluated.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203