Live threats
HighCritical Nginx Memory‑Corruption Flaws (CVE‑2026‑123007 & CVE‑2026‑113425) Allow Unauthenticated Remote Code Execution BreachOpenAI Agents Hack Hugging Face Model Repository, Exposing AI Supply‑Chain Risks Rule changeCleveland mayor's office introduces ordinance to award Flock Safety $2M no‑bid contract expansion DeadlineFarm Credit Administration amends employee payroll system of records under Privacy Act, effective Nov 24, 2026 CriticalCritical Memory‑Corruption Flaw (Java4Shell) Enables Unauthenticated Takeover of OpenJDK Runtime BreachAttackers Compromise Microsoft’s Agent‑Framework PyPI Package to Harvest Cloud Credentials Rule changeCNIL and Groupe VYV publish "La Voix des jeunesses" report on youth conversational AI use CriticalCritical Java4Shell (CVE‑2026‑114938) Heap‑Corruption Vulnerability Threatens Java Applications; Cloudflare Adds WAF Rules
Updated 03:25 UTC All intelligence →
BREACH WATCH BRIEF High 🐛 Vulnerability

Critical NGINX HTTP/2 Memory‑Corruption (CVE‑2026‑123007) Enables Remote Code Execution

A memory‑corruption flaw in NGINX’s HTTP/2 module (CVE‑2026‑123007) allows unauthenticated attackers to execute code as the NGINX worker. All unpatched NGINX Open Source 1.9.5‑1.31.8 and NGINX Plus builds with HTTP/2 enabled are in scope. The vulnerability highlights the need for continuous patch‑management evidence to satisfy audit and control‑assurance requirements.

SeverityHigh
Type🐛 Vulnerability
ConfidenceHigh
ReportedNov 18, 2026
Technology & SaaS organizations running web‑front‑ends, reverse proxies, load balancers, or Kubernetes ingress controllers that use NGINX with HTTP/2 Vulnerability Exploit

What happened

Qualys disclosed five related NGINX flaws, the lead one (CVE‑2026‑123007) being a memory‑corruption bug triggered by crafted HTTP/2 traffic. Researchers demonstrated remote code execution on the worker process, and a separate, unpatched Linux kernel issue can be chained to gain root. Public exploit code exists but requires direct HTTP/2 access and specific library conditions. Fixed NGINX releases were issued on the same day, and disabling HTTP/2 is a temporary mitigation.

Why it matters for trust and compliance

  • The flaw tests the control objective of maintaining secure configurations and timely vulnerability remediation, a core element of NIST CSF 2.0’s Protect function. Continuous evidence of patch status and configuration aligns with audit‑ready control mapping.
  • Provides concrete evidence for vulnerability‑remediation controls across frameworks.
  • Enables continuous monitoring of configuration (HTTP/2) and patch status for audit readiness.

Who is affected

organizations running web‑front‑ends, reverse proxies, load balancers, or Kubernetes ingress controllers that use NGINX with HTTP/2

Recommended actions

  1. Run an inventory scan to locate all NGINX instances with HTTP/2 enabled.
  2. Upgrade to the fixed NGINX version (1.30.7/1.31.9 or Plus 37.0.8.1/37.3.0.1) and restart the service.
  3. If immediate upgrade is not possible, disable HTTP/2 on the affected listeners.
  4. Document version, configuration, and restart timestamps as control evidence.

Details

CVEs
CVE-2026-123007

Regulations library

Every US state privacy law, on one map

24 states have a comprehensive privacy law in the library, alongside the EU, UK, US federal and global laws: 102 in all, each explained in plain words with its sources. Select a state to see what applies there.

  • In force
  • Coming into force
  • Sector laws
AK ME VT NH WA ID MT ND MN IL WI MI NY RI MA OR NV WY SD IA IN OH PA NJ CT CA UT CO NE MO KY WV VA MD DE AZ NM KS AR TN NC SC DC OK LA MS AL GA HI TX FL

Get the Breach Digest

The incidents that matter for your vendors and your data, analyzed for practitioners, in one email.