WebCritical 9.2Patch available
CVE-2026-123007
HTTP/2 heap overflow in NGINX enabling worker crash and potential RCE.
How scary is it?
updated 22 Nov 2026- Yes
Works without logging in1
No account and no user action needed (CVSS PR:N, UI:N).
- Yes
Reachable over the network1
Can be attacked remotely (CVSS AV:N).
- Yes
Proof-of-concept code is public2
37 GitHub proofs of concept. GitHub proofs of concept are unvetted: some are fake or carry malware. No Exploit-DB entry or Metasploit exploit module on record.
- None known
Attacks seen in the wild1
None reported that we know of. CISA's SSVC assessment says exploitation: none.
- No
On CISA's exploited list3
Not in the catalog as of our last sync.
Scare-o-meter
Act this week
Serious and within reach of attackers. Schedule the fix this week.
- Low signal
- Routine patch
- Act this week
- Drop everything
Why: Public proof-of-concept code exists for a network-reachable flaw; CVSS 9.2.1 Read from the same rule that decides our alert emails.
Are you affected? only if all are true
You run one of these 2 products in an affected versionF5 NGINX Open Source / F5 NGINX Plus
F5 NGINX Open Source: >= 1.31.0 and < 1.31.9, >= 1.30.0 and < 1.30.7, >= 1.9.5 and < *
F5 NGINX Plus: >= 37.1.0 and < 37.3.0.1, >= 37.0.0 and < 37.0.8.1, >= R33 and < *
As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.
See the affected products table · Source 1
An attacker can reach it over the network
CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.
Source 1
Specific conditions are met that the attacker does not control
CVSS attack complexity: High (AC:H). Needs specific conditions, a race or a particular configuration. The CVE record does not always say which.
Source 1
Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.
What to do
Per our analysisA patch is available
The CVE record we hold states no fixed release number. See the advisories in the references.
Recommendation, AI-writtenApply vendor fixes or upgrade NGINX immediately; disable HTTP/2 if you cannot patch now.
Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.
Fix reported in the news, AI summaryNGINX Plus 37.1.0 - 37.2.0.1 37.3.0.1; NGINX Plus 37.0.0 - 37.0.7.1 37.0.8.1; NGINX Plus R34 - R36 None; NGINX Open…
NGINX Plus 37.1.0 - 37.2.0.1 37.3.0.1; NGINX Plus 37.0.0 - 37.0.7.1 37.0.8.1; NGINX Plus R34 - R36 None; NGINX Open Source 1.31.0 - 1.31.8 1.31.9; NGINX Open Source 1.9.5 - 1.30.6 1.30.7
Written by a language model from the linked news pages only, and not updated when they change. It can be wrong: read the sources.
Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.
Major vulnerability. NGINX is a ubiquitous web server/reverse proxy; an HTTP/2 RCE/crash could disrupt web infrastructure across most organizations and attract broad attention.
- CVSS
- 9.2Criticalscored by the publisher (CNA)
- Exploited in the wild
- Not knownUnvetted proof-of-concept code on GitHub; not in CISA KEV
- EPSS
- 29.9%chance of exploitation in the next 30 daystop 2% of scored CVEsFIRST score of 21 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 18 Nov 2026analysed here 19 Nov 2026
In the news
Reported by 9 security news and advisory sources since 2026-11-18. Last widely reported 20 Nov 2026.
AI summary of the linked sources, written 22 Nov 2026
The most impactful of the five findings, CVE-2026-123007, allows an unauthenticated attacker to execute commands on an affected nginx server with HTTP/2 enabled.
- Impact
- The resulting memory corruption can disclose data, interrupt service, and execute code with the nginx worker process's permissions.
- Ease of exploit
- Leveraging CVE-2026-123007 for RCE requires a significant amount of network traffic to be transmitted, approximately 128 GB of HTTP/2 data, and available network bandwidth and connection timeouts place practical limitations on Internet exploitation.
- Root cause
- HTTP/2 flow-control memory corruption caused by an integer underflow.
- Fix
- NGINX Plus 37.1.0 - 37.2.0.1 37.3.0.1; NGINX Plus 37.0.0 - 37.0.7.1 37.0.8.1; NGINX Plus R34 - R36 None; NGINX Open Source 1.31.0 - 1.31.8 1.31.9; NGINX Open Source 1.9.5 - 1.30.6 1.30.7
Summary written from: rapid7.com, xint.io, cyberscoop.com. Other coverage: theregister.com, thehackernews.com, helpnetsecurity.com, infosecurity-magazine.com, bsi.bund.de, cert.europa.eu.
Written by a language model from those pages only, and not updated when they change. It can be wrong: read the sources.
Summary
Impact
HTTP/2 flow-control integer underflow leads to heap buffer overflow allowing worker crash, memory corruption, and possible remote code execution if ASLR is bypassed.
Triage
- Attack surface
- Server-side
- Exploitable
- At runtime
- Attack vector
- network
- Can a WAF block it?
- No. See why
Executive summary (AI-written)
A critical vulnerability (CVE-2026-123007) has been identified in NGINX, which could enable remote code execution and lead to major disruptions in web services. With a CVSS score of 9.2, this issue presents a significant risk for organizations that utilize NGINX as a web server or reverse proxy. Given NGINX's prevalence in web infrastructure, this vulnerability could impact a wide range of businesses, potentially leading to service outages and compromising sensitive data. Immediate attention is required to mitigate risks associated with this critical flaw.
Technical analysis (AI-written)
CVE-2026-123007 is a high-severity vulnerability affecting NGINX, resulting from an HTTP/2 flow-control integer underflow. This condition allows for a heap buffer overflow, which can lead to memory corruption and a crash of the NGINX worker processes. If an attacker can exploit this vulnerability, they may execute arbitrary code, especially if Address Space Layout Randomization (ASLR) is bypassed. Affected systems include not only NGINX Open Source and NGINX Plus but also OpenResty and various nginx-based ingress controllers across multiple Linux distributions like Ubuntu and RHEL. The exploitation of this vulnerability primarily relies on sending specially crafted HTTP/2 requests, which highlights an attack vector that could be leveraged from external sources. The complexity of exploitation is classified as medium, requiring a combination of skill and knowledge about web protocols and the targeted NGINX deployment. To mitigate this vulnerability, organizations must take immediate action by applying the available vendor patches. Where patching is not immediately feasible, an interim solution would be to disable HTTP/2 support in affected NGINX installations. It is crucial for organizations to prioritize these actions as the widespread nature of NGINX usage means that failure to address the issue swiftly could lead to severe operational impacts, including web service disruptions and potential data breaches. Security teams should not only focus on patching but also conduct thorough testing post-implementation to ensure that no further vulnerabilities are introduced during the upgrade process. Additionally, establishing robust monitoring for unusual HTTP/2 traffic patterns can help identify potential exploitation attempts before they escalate. Organizations should stay informed about updates and follow best practices for web server security to further bolster their defenses against such vulnerabilities.
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| F5 NGINX Open Source | >= 1.31.0 and < 1.31.9>= 1.30.0 and < 1.30.7>= 1.9.5 and < *Vendor says fixed in: not stated | |
| F5 NGINX Plus | >= 37.1.0 and < 37.3.0.1>= 37.0.0 and < 37.0.8.1>= R33 and < *Vendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- NGINX Open Source
- NGINX Plus
- OpenResty
- nginx-based ingress controllers
- Linux distros bundling nginx (Ubuntu, RHEL, etc.)
Fix and mitigation
Action required
Immediate action required
WAF and other mitigations
Can a WAF block it? No. This is an out-of-bounds write, a memory-corruption bug. Generic WAF rules do not recognise the input that triggers it; only a rule written for this specific CVE can, and only if the triggering request has a recognisable shape.
Also consider: patch
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Not listed as of our last sync.
- Public exploit code
- Unvetted proof-of-concept code on GitHub: 37 GitHub proofs of concept
- CISA SSVC
- exploitation none, automatable no, technical impact totalAssessed by CISA 18 Nov 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
GitHub proofs of concept
- sfewer-r7/CVE-2026-123007285 stars
- arkrwn/NGINX2Root-CVE-2026-12300710 stars
- HOSTED-POWER/nginx2root-patches9 stars
- WormW/nginx2root-rce-lab5 stars
and 33 more repositories
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
Timeline
- 18 Nov 2026First proof-of-concept repository on GitHub (unvetted)
- 18 Nov 2026CISA SSVC assessment: exploitation nonesame day later
- 18 Nov 2026Published1 day later
- 19 Nov 2026CVE record last updated1 day later
- 19 Nov 2026Analysed by vulneraibility.comsame day later
Common questions
Is CVE-2026-123007 being exploited?
Not confirmed. CVE-2026-123007 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 30% probability of exploitation in the next 30 days.
How severe is CVE-2026-123007?
CVE-2026-123007 is rated Critical with a CVSS score of 9.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-123007?
Yes. A fix has been recorded for CVE-2026-123007. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-123007 affect?
CVE-2026-123007 affects NGINX Open Source, NGINX Plus, OpenResty, nginx-based ingress controllers, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-123007?
Apply vendor fixes or upgrade NGINX immediately; disable HTTP/2 if you cannot patch now.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
16 references in the CVE record, grouped by the tags the record gives them.
Patches (1)
- my.f5.com /manage/s/article/K000163926
Other links (15)
- wiz.io /blog/nginx-http2-rce-vulnerabilities
- news.ycombinator.com /item?id=50547374
- github.com /nginx/nginx/commit/b89c4100bf6762a45e4a6463eaf4b70368277c94
- ubuntu.com /security/CVE-2026-123007
- github.com /advisories/GHSA-m4q8-cf44-f42r
- github.com /openresty/openresty/issues/1165
Show 9 more
- github.com /nginx/nginx/issues/2002
- nginx.org /en/CHANGES
- github.com /chainguard-forks/ingress-nginx/pull/69
- cyberscoop.com /nginx-critical-vulnerabilities-exploits/
- rapid7.com /blog/post/ve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-r
- xint.io /blog/nginx2root-remote-code-execution
- nginx2root.com
- access.redhat.com /security/cve/cve-2026-123007
- github.com /Azure/aks-app-routing-operator/issues/623
Also tracked as GHSA-m4q8-cf44-f42r (OSV).
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- OSV: advisory aliases and downstream package versions
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Security news coverage and the AI summary of it: the pages linked in that section.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.