An explainer on a memory-corruption vulnerability in NGINX's HTTP/2 module (CVE-2026-123007). It covers what happens, who is affected and how to respond, from a defender's point of view and without attack steps.
- CVE
- CVE-2026-123007 (memory corruption in NGINX's ngx_http_v2_module)
- Severity
- CVSS v4 9.2 (Critical) / CVSS v3.1 8.1 (High; vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H). Assigned by F5
- Type
- Integer underflow (CWE-191), out-of-bounds write (CWE-787). Heap buffer overflow
- Impact
- Worker process crash (typical). Memory corruption. Code execution is also possible where ASLR is disabled or bypassed (F5)
- Affected
- NGINX Plus and NGINX Open Source in configurations that use HTTP/2. Open Source from 1.9.5, before 1.31.9 (1.31 line) or 1.30.7 (1.30 line)
- Fix
- Open Source: 1.31.9 / 1.30.7. Plus: 37.3.0.1 / 37.0.8.1
- Published
- 18 November 2026 (F5's CVE record published 15:23 UTC)
- Exploitation
- Not in KEV (checked 19 November). CISA's assessment: exploitation none
The same release also contains other security fixes
The nginx.org change log for 1.31.9 (18 November 2026) lists several other security fixes besides this one. Updating to 1.31.9 or 1.30.7 brings those too. For the scope of the other CVEs, see nginx.org's list and F5's advisories.
What the vulnerability is
According to F5, in configurations that use HTTP/2, when NGINX processes certain traffic the flow-control window (the HTTP/2 mechanism that regulates how much data may be sent) can exceed the allowed threshold. That leads to a buffer overflow on the heap (dynamically allocated memory), which typically ends in a crash of the NGINX worker process.
- The attack is over the network, needs no authentication and no user interaction. Attack complexity is rated High.
- F5 says code execution is possible where ASLR (a defence that randomises memory layout) is disabled or the attacker can bypass it. Where ASLR works, the likely outcome is a process crash (this site's reading of F5's description). Do not rely on that; update.
- F5 says there is no control plane exposure; it is a data plane issue only.
- Neither F5 nor nginx.org publishes how to build the traffic, and this site does not either.
Scope
| Item | Detail |
|---|---|
| Products | NGINX Plus, NGINX Open Source (configurations that use HTTP/2) |
| Affected (Open Source) | From 1.9.5. 1.31 line before 1.31.9, 1.30 line before 1.30.7 (nginx.org lists 1.9.5 through 1.31.8) |
| Affected (Plus) | 37.1.0 before 37.3.0.1, 37.0.0 before 37.0.8.1. The CVE record also lists R33 (no fixed version given) |
| Fix | Open Source 1.31.9 and 1.30.7. Plus 37.3.0.1 and 37.0.8.1 |
| Workaround | None (F5) |
| Note | F5 does not evaluate versions past End of Technical Support |
- For F5 products that contain NGINX (F5 WAF for NGINX, F5 DoS for NGINX, NGINX Gateway Fabric, NGINX Ingress Controller and others), check the affected versions in F5's advisory table.
- This site could not confirm fixes for lines older than 1.30 (such as 1.28). nginx.org lists the affected range as 1.9.5 through 1.31.8 and the fixed versions as 1.31.9+ and 1.30.7+. If you run an older line, plan a move to a line that has a fix.
How to check whether you are affected
Check the NGINX version
On the server, nginx -v prints the version. For Plus, check the product version (37.x, R3x). For NGINX inside containers or an Ingress Controller, work out the NGINX version from the image version.
Check whether HTTP/2 is enabled
In your configuration, look for http2 on the listen directive or an http2 on; line (the syntax differs by version, so check the official documentation). Configurations that use HTTP/2 are the affected ones.
List the internet-facing entry points
List NGINX instances reachable from outside (reverse proxies, load balancers, ingress). The security inventory checklist can help.
What to do today
Update to a fixed version (top priority)
Open Source: 1.31.9 on the 1.31 line, or 1.30.7 or later on the 1.30 line. Plus: 37.3.0.1 or 37.0.8.1 or later. Check your runbook for how to apply it (reload or restart, and ordering in redundant setups), and start with entry points exposed to the internet.
If you use a distribution package, check its advisory
NGINX installed from an OS package may be numbered differently, and fixes may arrive under other version numbers. Check the distribution's advisory to see whether a fix has shipped. While it has not, decide by your own policy whether to switch to nginx.org's official packages or wait for the distribution.
Check updates for products that include NGINX
Ingress Controllers, Gateway Fabric and WAF products carry their own version numbers apart from NGINX itself. Use F5's advisory to find the fixed versions.
Until you update (this site's advice)
There is no official workaround. Until you update, reduce unneeded public exposure and watch for an increase in worker process crashes (for example signal 11 entries in the error log). If you find crashes, speed up the update. Also check at the OS level that ASLR is enabled (on Linux it can be checked in the kernel settings).
Exploitation status
- As checked on 19 November 2026, CVE-2026-123007 is not in CISA's KEV catalog (Known Exploited Vulnerabilities).
- CISA's assessment on the CVE record (SSVC, 18 November 2026) is exploitation: none, automatable: no, technical impact: total.
- F5's CVE record does not say exploitation was observed.
- Things can move soon after publication. Check follow-up for a KEV addition or reports of exploitation.
Sources
- F5 — K000163926: NGINX ngx_http_v2_module vulnerability (CVE-2026-123007) (18 November 2026. The page is rendered with JavaScript and this site could not read its body by automated fetch; confirmed against the CVE record registered by F5)
- nginx.org — security advisories (affected 1.9.5 through 1.31.8, fixed 1.31.9 and 1.30.7) / CHANGES (1.31.9, 18 November 2026)
- CVE.org — CVE-2026-123007 (registered by F5; includes CISA's assessment)
- CISA KEV — Known Exploited Vulnerabilities Catalog (not listed as of 19 November)
No attack steps are included. Last checked: 19 November 2026.
Read next
- Practice: CVE remediation playbook / Security inventory checklist
- Judgement: Prioritising with CVSS, EPSS and KEV
- Terms: What is a CVE? / What is CVSS? / What is RCE?