Contact us
← Article questionsWhat’s the evidence?

CVEHit Business Advisory by IntegrityLab.ai

What’s the evidence?

NGINX HTTP/2 flaws can crash or take over web servers — CVE-2026-123007 and CVE-2026-123633: Business Triage

UPDATE: If records show a break-in, start incident response now. A government security center reports exploitation of an unspecified NGINX flaw that no other source has confirmed. Apply the fix for your affected NGINX build now. Check separately for the other three flaws even if HTTP/2 is off.

The reported finding

HTTP/2 flow-control memory corruption (CVE-2026-123007)

Original advisory →
Required conditions
NGINX Open Source 1.9.5 through 1.31.8, or an affected NGINX Plus release, with HTTP/2 turned on (ngx_http_v2_module).
Reported outcome
F5: the HTTP/2 flow control window can exceed the allowed threshold, leading to a heap buffer overflow, typically followed by a worker crash. Code execution is possible where ASLR is disabled or can be bypassed. Weaknesses named in the record: CWE-191 (integer underflow) and CWE-787 (out-of-bounds write). nginx.org severity: major. F5 CVSS 3.1 8.1 High; CVSS 4.0 9.2 Critical.

HTTP/2 use-after-free when proxying (CVE-2026-123633)

Original advisory →
Required conditions
NGINX Open Source 1.19.7 through 1.31.8, or an affected NGINX Plus release. HTTP/2 used for client connections, requests passed to a backend, and a worker process running low on worker_connections.
Reported outcome
F5: a specially crafted request can cause use-after-free in the worker process, leading to denial of service or code execution. Code execution is possible where ASLR is disabled or can be bypassed. Weakness named in the record: CWE-416 (use after free). nginx.org severity: medium. F5 CVSS 3.1 8.1 High; CVSS 4.0 9.2 Critical.

Fix guidance

  • nginx.org (@nginxorg on X): not vulnerable 1.31.9+ and 1.30.7+ for both CVEs. Both releases dated November 18, 2026.
  • NGINX Plus fixed releases, from F5 (@F5 on X): 37.3.0.1 and 37.0.8.1 (CVE-2026-123007); 37.2.0.1 and 37.0.7.1 (CVE-2026-123633). The 37.3.0.1 and 37.0.8.1 releases cover both. F5 names no fix for NGINX Plus R33 and later in the older release line. F5 lists no workaround for either CVE.
  • Restart NGINX after updating. A reload does not replace the running program.
  • Community Kubernetes ingress-nginx: retired. Final releases v1.15.1 (newest), v1.14.5 and v1.13.9, all March 19, 2026. No further security patches. Move to a maintained controller.
  • Exploitation report: WASOC advisory 20261119001 (Western Australian Government; the page shows no date beyond the advisory ID) says WASOC "has been made aware of exploitation in the wild for one or more" of five NGINX CVEs: CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810 and CVE-2026-113425. It does not say which CVE, when the exploitation happened or who reported it. It says WASOC has received no reports of exploitation on Western Australian Government networks.
  • No other source we checked on November 20, 2026 confirms that report. Cloudflare (@Cloudflare on X) says in its November 20, 2026 post that it had seen no reports of exploitation in the wild as of November 19.
  • Exploitation status: CISA (@CISAgov on X) SSVC in both CVE records, dated November 18, 2026: Exploitation none, Automatable no, Technical Impact total. Neither CVE is in CISA KEV catalog 2026.11.18, the latest catalog when rechecked on November 20, 2026. No KEV entry and Exploitation none do not prove no attacks occurred.
  • Rapid7 (@rapid7 on X), a credited reporter, published proof-of-concept code for CVE-2026-123007 on November 18, 2026. Rapid7 says its demonstration targeted a linux/amd64 Docker image running nginx 1.31.8 with HTTP/2 on. It says the method needs about 128 GB of HTTP/2 traffic, fails on links slower than about 300 Mbit/s because of NGINX's default one-hour connection limit, will likely not work where the HTTP/2 connection is proxied, and runs code with the worker process's permissions only. These sources report no proof of concept for CVE-2026-123633. This page does not link to exploit code directly; the Rapid7 disclosure it cites links to that proof of concept.
  • The same NGINX releases also fix CVE-2026-123634 (resolver), CVE-2026-121810 (HTTP/3) and CVE-2026-113425 (mail proxy). They need different settings, and turning off HTTP/2 does not block them. Updating to 1.31.9 or 1.30.7 fixes all of them.
  • Ubuntu USN-9159-1, November 19, 2026, fixes both CVEs: Ubuntu 26.10 nginx 1.30.4-7ubuntu1.2, 26.04 LTS 1.28.3-2ubuntu1.13, 24.04 LTS 1.24.0-2ubuntu7.20 and 22.04 LTS 1.18.0-6ubuntu14.23. Ubuntu 20.04 LTS and older get fixes through Ubuntu Pro.
  • Debian 13 (trixie) is fixed in nginx 1.26.3-3+deb13u11 (DSA-6642-1) for both CVEs. Debian 12 (bookworm) is still listed as vulnerable in the Debian security tracker, checked November 19, 2026.
  • These sources confirm no container image package fix. NVD status: Received (not yet analysed), checked November 18, 2026.

What IntegrityLab.ai can check

  • This advisory does not mean IntegrityLab.ai detects CVE-2026-123007 or CVE-2026-123633.
  • When enabled for an authorized assessment, IntegrityLab.ai's discovery records reachable web services and the server name they return. This gives your administrator a starting point. It does not currently offer a validated check for these CVEs, an HTTP/2 flaw test, confirmation of a package's fixes, or proof of compromise.
  • A displayed NGINX name or version is a clue, not proof of the installed build or fix status. A missing name does not rule NGINX out. If another server handles the public connection, its response does not show what runs behind it.

How to read the score

F5 (CVE record) CVSS 3.1: 8.1 (High). CVSS 4.0: 9.2 (F5): Critical. Use the conditions and update history alongside the score to set your priorities.

Sources and vendor guidance

← Back to article questions

How can we help?

Initial enquiries only. Omit passwords, access tokens, security reports or other sensitive information. We’ll arrange secure sharing if needed.

Privacy & data handling ↗. Submitting this form does not authorise an assessment.

Checking enquiry availability…