nginx: critical HTTP/2 integer underflow (CVE-2026-123007) allows remote code execution, fixes released
Published 18/11/2026 17:24
Timeline
4 events over 2 h
- 18/11/2026 14:56First report+2 h
- 18/11/2026 17:07CorroboratedNCSC-NL advisories+0 min
- 18/11/2026 17:07ConfirmedNCSC-NL advisories+16 min
- 18/11/2026 17:24Published on WatchtowerPro CISO
In short
A remote, unauthenticated attacker can send crafted HTTP/2 requests to an nginx server and cause memory corruption, which can leak data, stop the service or run code with the nginx worker's permissions. Rapid7 reports a working proof of concept against nginx 1.31.8, and NCSC-NL reports that F5 has fixed NGINX Plus and Open Source. Install the fixed release for your branch; the exact fixed versions were not found in the signals.
Shodan estimates about 56.9 million internet-facing nginx servers worldwide, 8.3 million of them in the EU (18/11/2026); how many run an affected version is not yet known.
How bad is it
Critical: an unauthenticated remote attacker can run code on an nginx server with HTTP/2 enabled by sending crafted requests.
Confirmed by the vendor or a CERT - no exploitation reported yet.
Severity score
CVSS 4.0 from NVD, from f5.com, read 18/11/2026.
What an attacker needs
- Internet access to itEnough
- A loginNot needed
- A user to clickNo
- Special settingsUsually yes
Red helps the attacker, blue holds them back, grey is not published yet.
If it works, an attacker can
- Run their own code on the system
- Read the data it holds
- Change or delete that data
- Take it offline
Type: remote code execution.
A score is the worst case for the flaw, not a verdict on any one system. How we score · ReconX customers see which of their own systems are affected.
Affected versions
- nginx with HTTP/2 enabled, including nginx 1.31.8 (shown vulnerable by Rapid7's proof of concept). NCSC-NL says NGINX Plus and NGINX Open Source are affected. The exact affected version ranges were not found in the signals.
Fixed in
- NCSC-NL reports that F5 has released fixes for NGINX Plus and NGINX Open Source. The fixed version numbers were not found in the signals; check the F5 and nginx advisories.
What to do now
- Check the F5 and nginx security advisories for CVE-2026-123007 and update NGINX Open Source and NGINX Plus to the fixed release for your branch as soon as possible. Do not rely on 1.31.7 or 1.30.6, which were listed as fixes for other CVEs, and 1.31.8 is vulnerable.
- Rapid7 and NCSC-NL expect exploitation, so treat internet-facing servers with HTTP/2 enabled as the first priority.
- No workaround was found in the signals. Disabling HTTP/2 on exposed servers may reduce exposure, but no signal says so, so confirm with the vendor advisory.
- Ask your hosting provider whether they have patched.
ReconX customers see the full notice - and their own systems
Our customers are alerted at every phase. Until a patch exists, the ReconX agent watches their servers from the inside for anomalies, and our outside view - the attacker's view - shows which systems to fix first.
In ReconX: the full analysis, 5 open questions, followed up as sources answer and all 4 sources with their dates. And technology matching: which of your systems run nginx, at which version, fixed or not - and what each one needs.
Main sources
NCSC-2026-0506 [1.00] [H/H] Kwetsbaarheden verholpen in NGINX door F5 Networks CERT · CVE-2026-123007: Critical NGINX HTTP/2 Integer Underflow Leads to RCE (FIXED) Research · nginx security advisories Research