Contact us
← CVEHit Business AdvisoryNGINX HTTP/2 flaws can crash or take over web servers — CVE-2026-123007 and CVE-2026-123633: Business Triage

CVEHit Business Advisory by IntegrityLab.ai

Published · Updated

NGINX HTTP/2 flaws can crash or take over web servers — CVE-2026-123007 and CVE-2026-123633: Business Triage8.1/10High · CVSS 3.1F5 (CVE record)Fix available1.31.9 / 1.30.7 · Plus 37.3.0.1 / 37.0.8.1CISA 123007CVE.org sourceNo KEV 123007Checked Nov 20CISA 123633CVE.org sourceNo KEV 123633Checked Nov 20

Update NGINX Open Source to 1.31.9 or 1.30.7, or NGINX Plus to a fixed 37.x release. Research: primary sources retrieved November 18, 2026; Linux distribution packages rechecked November 19, 2026; exploitation status rechecked November 20, 2026.

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.

Check these three things.

  1. System owner: confirm whether each NGINX server, including NGINX inside other products, needs NGINX 1.31.9 or 1.30.7.
    Affected versions and fixes
    • CVE-2026-123007: NGINX Open Source 1.9.5 through 1.31.8 is affected (nginx.org).
    • CVE-2026-123633: NGINX Open Source 1.19.7 through 1.31.8 is affected (nginx.org).
    • Fixed releases for both: NGINX Open Source 1.31.9 and 1.30.7, released November 18, 2026.
    • NGINX Plus, from F5's CVE records:
      • CVE-2026-123007: 37.1.0 before 37.3.0.1 and 37.0.0 before 37.0.8.1 are affected. Fixed: 37.3.0.1 and 37.0.8.1.
      • CVE-2026-123633: 37.1.0 before 37.2.0.1 and 37.0.0 before 37.0.7.1 are affected. Fixed: 37.2.0.1 and 37.0.7.1.
      • F5's records also list NGINX Plus R33 and later releases as affected and name no fixed release in that line.
      • F5 does not evaluate versions past End of Technical Support.
    • NGINX is often built into other products: load balancers, Kubernetes ingress controllers, appliances and container images. Each carries its own NGINX copy and needs its own fix.
    • The community Kubernetes ingress-nginx controller is retired. Its final releases came out on March 19, 2026 (v1.15.1, v1.14.5 and v1.13.9). All three build on NGINX 1.27.1, inside both affected ranges, and turn HTTP/2 on by default. The project says it will receive no further releases or security patches.
    • A Linux distribution package may carry a fix under an older-looking version number. Ubuntu and Debian 13 now ship fixed packages. Debian 12 had no fix when checked on November 19, 2026.
    • Record for each server:
      • Installed version or package.
      • Source of that record.
      • Date checked.
  2. Operations owner: check whether HTTP/2 is turned on, and whether NGINX passes requests to backend servers.
    When the risk applies
    • CVE-2026-123007 applies when HTTP/2 is turned on. No other setting is required.
    • CVE-2026-123633 applies when HTTP/2 is used for client connections, NGINX passes requests to a backend server, and a worker process is running low on connection slots (worker_connections).
    • The CVSS vector includes AV:N, meaning network-reachable, including internal networks. It is not proof of Internet exposure.
    • A server in front of NGINX, such as a CDN or another proxy, may handle HTTP/2 itself. That does not show whether NGINX behind it uses HTTP/2.
    • A server that had HTTP/2 on while running an affected version was exposed for that time, even if it is fixed now.
  3. Security owner: check records for unexplained NGINX worker crashes or unexpected programs started by NGINX.
    What the records can show
    • F5 says the usual result is a crash of an NGINX worker process. Code execution is possible where memory-layout protection (ASLR) is off or can be bypassed.
    • Records to review:
      • NGINX error logs for worker exits and segmentation faults.
      • System crash records.
      • Security alerts.
      • Unexpected processes started by the NGINX worker account.
      • Unexpected outbound connections.
    • Limits:
      • Workers can crash for unrelated reasons.
      • Clean records do not prove no attack happened.
      • Missing records leave the question open.

If records show a break-in, start incident response now. Apply the fix for your affected NGINX build. Check separately for the other three flaws even if HTTP/2 is off.

Do Now

  • System owner: update NGINX Open Source to 1.31.9 or 1.30.7, or NGINX Plus to 37.3.0.1 or 37.0.8.1, then restart NGINX.
    Proof the update is done
    • Completion evidence for each server:
      • Version or package installed after the update.
      • Source of that record.
      • Date checked.
    • A configuration reload alone does not replace the running program. Confirm the running version after a restart.
    • For a distribution package claiming a fix below 1.30.7, the distribution's notice naming both CVEs.
  • Operations owner: where an immediate update is not possible, turn off HTTP/2 on affected listeners until the update is done.
    What to know
    • F5 lists no workaround. F5 describes both flaws as affecting configurations that use HTTP/2, so with HTTP/2 off the stated condition is not met. This is a stopgap, not the fix.
    • Services that need HTTP/2, such as gRPC, cannot use this stopgap.
    • On the retired community ingress-nginx controller, HTTP/2 is on by default (use-http2). No fixed release will come. Plan a move to a maintained controller.
  • Provider: ask each vendor whose product or hosting includes NGINX whether it is affected and when a fix ships.
    What to ask
    • Ask for:
      • Which NGINX version the product or service runs.
      • Whether HTTP/2 is on.
      • The fix date.
    • Keep the reply as evidence.

Do Next

  • Security owner: recheck CISA, F5 and WASOC for changes to the exploitation status.
    What to recheck
    • CISA's assessment in each CVE record, dated November 18, 2026.
    • The CISA Known Exploited Vulnerabilities (KEV) catalog. None of the five flaws appeared in catalog 2026.11.18 when we checked on November 20, 2026.
    • WASOC advisory 20261119001, which names no exploited CVE yet.
    • nginx.org security advisories and F5 articles K000163926 and K000163928.
    • Date of each recheck.

Check your own records.

  • Use your approved AI tool.
  • Require evidence. Flag unknowns.

Read the prompt

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

Need an independent review of your public exposure?

See IntegrityLab.ai →

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…