Skip to main content
Menu
Early warnings

Early warning

F5 discloses NGINX HTTP/2 flaw CVE-2026-123007 that can allow code execution

F5 says the decade-old HTTP/2 flaw CVE-2026-123007, dubbed "nginx2root," lets unauthenticated attackers run code on NGINX servers with HTTP/2 enabled, and fixed versions 1.31.9 and 1.30.7 are now available.

SZB-4bd5930715First seen Confirmed Summary written by a modelVulnerability

Sources18Confirmed

Summary

F5 says the decade-old HTTP/2 flaw CVE-2026-123007, dubbed "nginx2root," lets unauthenticated attackers run code on NGINX servers with HTTP/2 enabled, and fixed versions 1.31.9 and 1.30.7 are now available. The article reports that neither F5 nor the researchers who tested it have seen attacks exploiting the flaw so far.

What to do

  • Upgrade NGINX Open Source to 1.31.9 or 1.30.7, or NGINX Plus to a fixed build.

  • Restart NGINX fully or use the live binary upgrade, since a reload leaves the old executable running.

  • Check whether HTTP/2 is enabled on your servers, including origins behind a CDN.

Timeline

  1. Made public by Mastodon
  2. First seen by cve.now
  3. Confirmed as CVE-2026-1230071 day
  4. Record last updated

Evidence 18

  1. Social
    Mastodon
    “CVE-2026-123007 enables NGINX remote code execution over HTTP/2, and a public PoC exploit is out.”
    +4 more: Mastodon, Mastodon, Mastodon, Mastodon
  2. Social
    Mastodon
    “Researchers behind NGINX2Root report five nginx flaws, including a critical HTTP/2 issue that may enable remote code execution.”
  3. Social
    Mastodon
    “Tracked as CVE-2026-123633 and CVE-2026-123007, both flaws carry a CVSS score of 9.2 and affect NGINX servers with HTTP/2 enabled.”
  4. Social
    Mastodon
    “NGINX shipped 1.31.9 (mainline) and 1.30.7 (stable) today with fixes for 10 CVEs.”
  5. Social
    Mastodon
    “Two critical Nginx flaws in the HTTP/2 implementation let an unauthenticated attacker run code on the server.”
  6. Press
    The Hacker News
    “A flaw in NGINX's HTTP/2 support can allow an attacker to run code on servers with HTTP/2 enabled, without needing to log in.”
  7. Social
    Mastodon
    “ALERTE Multiples vulnérabilités dans F5 NGINX (18 novembre 2026)”
  8. Social
    Mastodon
    “🚨 BREAKING: A 10-YEAR-OLD FLAW IN # NGINX COULD LET HACKERS TAKE OVER WEB SERVERS WITHOUT A PASSWORD.”
  9. Social
    Bluesky
    “Astronomer is reporting an Incident since 19:17 UTC”
  10. Social
    Mastodon
    “🚨 Rapid Response: Five NGINX flaws (nginx2root, CVSS v4.0 9.2).”
  11. Social
    Mastodon
    “NGINX patched five vulnerabilities, including a critical CVSS 9.2 integer underflow in the HTTP/2 module.”
  12. Social
    Mastodon
    “Right, so this time it's Nginx CVEs with RCEs ...”
  13. Social
    oss-security
    “CVE-2026-123633, CVE-2026-123007: nginx RCE via HTTP/2”
  14. Social
    Mastodon
    “Based on a quick audit of my home and hobby servers, it doesn't appear to me as though this affects Nginx in the default Debian configuration?”
  15. Social
    Mastodon
    “nginx fixed CVE-2026-123007, an HTTP/2 memory-corruption bug that can let an unauthenticated attacker run code.”
  16. Social
    Mastodon
    “Includes additional details about the vulnerabilities and how to measure your nginx exposure in Censys”
  17. Social
    oss-security
    “Re: Another (?) Linux kernel SCTP vuln undisclosed”
  18. Social
    Mastodon
    “NGINX Vulnerabilities: Five Critical Flaws Put Web Servers at Risk”

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about F5 discloses NGINX HTTP/2 flaw CVE-2026-123007 that can allow code execution

Has NGINX confirmed it?

Yes. Confirmed as CVE-2026-123007.Source: Mastodon, Mastodon, Mastodon, Mastodon, Mastodon, The Hacker News, Mastodon, Mastodon, Bluesky, Mastodon, Mastodon, Mastodon, oss-security, Mastodon, Mastodon, Mastodon, oss-security, Mastodon

What should NGINX and Astronomer users do?

Upgrade NGINX Open Source to 1.31.9 or 1.30.7, or NGINX Plus to a fixed build. Restart NGINX fully or use the live binary upgrade, since a reload leaves the old executable running. Check whether HTTP/2 is enabled on your servers, including origins behind a CDN.

Does it have a CVE?

Yes. It is tracked as CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810 and CVE-2026-113425.Source: CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810, CVE-2026-113425