International
The Morning Dev

Only the news worth knowing

‹
 
A66/100

Vulnerability · high · CVSS 8.1

Unauthenticated remote code execution in NGINX HTTP/2 (CVE-2026-123633 and CVE-2026-123007)

Tier A · Patch today – Before you go home

Who’s exposed: NGINX servers with HTTP/2 enabled

Tier A because: Core infrastructure or popular tool AND remote, no login AND full takeover

Reach

Attack

Damage

Fix

Popular tool · Remote, no login · Full takeover

What to do

  1. Update NGINX to a patched release that fixes CVE-2026-123633 and CVE-2026-123007

The Brief

  • Two critical NGINX HTTP/2 flaws, CVE-2026-123633 and CVE-2026-123007, can allow unauthenticated remote code execution under certain conditions.
  • Xint reports five critical NGINX vulnerabilities and says it found them using AI models; Wiz says it separately found the same flaws.
  • Rapid7 describes CVE-2026-123007 as an integer underflow in nginx HTTP/2, and marks it as fixed.

Why it matters

Attackers who can reach an affected NGINX server with HTTP/2 enabled may be able to run commands on it, putting the websites, APIs and sensitive data it handles at risk.

The checklist behind the tier

Checklist · 4 of 10 yes
YesHits tech teamsJudgment: NGINX is a web server and reverse proxy that ops and IT teams run in production.
NoCore infrastructureJudgment: NGINX is a single popular product, not foundational infrastructure like OpenSSH or the Linux kernel.
YesPopular toolJudgment: NGINX is a mainstream, widely deployed web server used by many teams.
NoExploited in the wildSources describe researcher discovery (Techmeme/Forbes, Wiz, LWN); none reports observed attacks or KEV listing.
NoPublic exploitWiz and Rapid7 describe the flaws; no source says exploit code or a PoC was published.
YesRemote, no loginCVSSCVE-2026-123633: CVSS 8.1 – network, no privileges, no user interaction
YesFull takeoverCVSSCVE-2026-123633: CVSS rates confidentiality and integrity impact high
NoSecrets exposedNo source reports stolen credentials, keys, configs or customer data; only exploitability is described.
NoSupply chainSources describe vulnerabilities in NGINX code, not malicious code shipped through a trusted channel.
NoNo fix yetRapid7 titles its post "(FIXED)" and Xe Iaso says admins rebuilt and patched systems after the release.

The official record

From CVE.org, CISA’s Known Exploited Vulnerabilities catalog, FIRST EPSS and the GitHub Advisory Database. Where these answer a checklist fact, they win over the reporting.

  • CVE-2026-123633 ↗CVSS 8.1 high AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

    NGINX ngx_http_v2_module vulnerability

    Exploited
    Not in CISA’s exploited catalog
    Weakness
    CWE-416

    NVD

  • CVE-2026-123007 ↗CVSS 8.1 high AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

    NGINX ngx_http_v2_module vulnerability

    Exploited
    Not in CISA’s exploited catalog
    Weakness
    CWE-191, CWE-787

    NVD

Timeline

  1. Rapid7 and F5 disclose CVE-2026-123007

  2. Wiz publishes details of CVE-2026-123633 and CVE-2026-123007

  3. Xe Iaso's blog

    "No way to prevent this" say users of only language where this regularly happens

  4. Rapid7 Cybersecurity Blog

    CVE-2026-123007: Critical NGINX HTTP/2 Integer Underflow Leads to RCE (FIXED)

  5. Wiz Blog | RSS feed

    Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007

  6. LWN.net

    NGINX2Root: Remote Code Execution vulnerabilities in nginx

  7. Techmeme

    Cybersecurity company Xint says it found RCE vulnerabilities in Nginx using GPT 6.1 Sol and GPT-6 Luna; Wiz says it had separately found the same flaws (Thomas Brewster/Forbes)

  8. DEV Community: ai

    Dev News Digest: 18 Nov 2026, 18:00

Full coverage · 6 sources

First seen · 6 sources · Full story page · How tiers are decided