CVE-2026-123007
NGINX ngx_http_v2_module vulnerability
No known exploitation. No EPSS score yet. Fixed versions are out.
No public exploit knownFix2 products4 fixed builds listed below
No ready-made check. Neither Nuclei nor OpenVAS has one for this CVE yet.
What to do
Find your product and version, then upgrade to the build on the right.
- F5 NGINX PlusAffected: ≥ 37.1.0, < 37.3.0.1Upgrade to: 37.3.0.1Affected: ≥ 37.0.0, < 37.0.8.1Upgrade to: 37.0.8.1Affected: R33Upgrade to: not statedStated by: CVE record
- F5 NGINX Open SourceAffected: ≥ 1.31.0, < 1.31.9Upgrade to: 1.31.9Affected: ≥ 1.30.0, < 1.30.7Upgrade to: 1.30.7Affected: 1.9.5Upgrade to: not statedStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
Steps
Written by AI from the record- Check which NGINX or NGINX Plus version you are running and whether HTTP/2 is enabled.
- If you run NGINX, upgrade to 1.31.9 or 1.30.7 (or later).
- If you run NGINX Plus, upgrade to 37.3.0.1 or 37.0.8.1 (or later).
- There is no workaround available, so patching is the only fix — schedule it soon rather than urgently.
- Ensure ASLR (Address Space Layout Randomization) is enabled on the server's operating system as an extra layer of defense while you patch.
What it is
From the CVE record
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.
In plain language
Written by AI from the recordA bug in NGINX's HTTP/2 handling can crash the web server or, in the worst case, let an attacker run code on it, but there's no sign anyone is actually exploiting it yet so you should patch soon without panicking.
A flow-control integer overflow (CWE-191) in ngx_http_v2_module can push the HTTP/2 window past its bound, causing a heap buffer overflow (CWE-787) that typically crashes the worker process and may permit remote code execution if ASLR is disabled or bypassed.
If you're affected
- Website/service outage
- Worker process crashes
- Possible remote code execution
- Service disruption during attack
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
No EPSS score yet. New CVEs are usually scored within a few days.
Lifecycle
9 events over 1 day, from the signal feeds we watch.
- Analysis publishedNGINX HTTP/2 remote code execution (CVE-2026-123007, CVE-2026-123633): what is confirmed and how to check your servers
- Workaround availableworkaround available, workaround available, published, weakness classified, att&ck mapped, record updated, record updated
Affected products
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Scored 8.1 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality HighTotal information disclosure — all data in the component is compromised
- Integrity HighTotal loss of integrity — attacker can modify any data in the component
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
- Initial AccessT1190Exploit Public-Facing Applicationhigh confidence
- Privilege EscalationT1068Exploitation for Privilege Escalationhigh confidence
Sources
References in the record
- my.f5.com/manage/s/article/K000163926
- access.redhat.com/security/cve/cve-2026-123007
- cyberscoop.com/nginx-critical-vulnerabilities-exploits/
And 13 more references. See all after sign-in
Analysis on the cve.tools blog
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for NGINX Plus, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI