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 CriticalJava4Shell OpenJDK Base64 Decoder Flaw (CVE‑2026‑114938) Enables Remote Code Execution on Select CPUs BreachCredential‑Harvesting Attack Forces Japan’s Fugaku Supercomputer Offline Rule changeEuropean Commission launches call for expression of interest for European AI providers CriticalApache Roller Remote Code Execution (CVE‑2026‑129448) Actively Exploited in the Wild
Updated 03:25 UTC All intelligence →
BREACH WATCH BRIEF Critical 👤 Vulnerability

Critical Remote Code Execution Vulnerability (CVE-2026-123007) in NGINX HTTP/2 Allows Unauthenticated Attackers to Execute Code

A decade‑old flaw in NGINX’s HTTP/2 stack (CVE‑2026‑123007) enables unauthenticated attackers to execute arbitrary code with root privileges. The issue affects all NGINX versions from 1.9.5 through 1.31.8 and is fixed in 1.31.9/1.30.7. It highlights the need for robust vulnerability‑management controls and timely patching to maintain audit‑ready evidence.

SeverityCritical
Type👤 Vulnerability
ConfidenceHigh
ReportedNov 18, 2026
Technology & SaaS TECH_SAAS Vulnerability Exploit

What happened

Researchers disclosed CVE‑2026‑123007, a heap‑overflow in NGINX’s HTTP/2 handling that can be triggered without authentication. Exploitation grants arbitrary code execution as root. F5 released patches (1.31.9, 1.30.7) on 19 Nov 2026 and advised immediate upgrade or temporary HTTP/2 disablement.

Why it matters for trust and compliance

  • The incident underscores the importance of a continuous vulnerability‑management control that maps to multiple frameworks, ensuring that unpatched flaws are identified, prioritized, and remediated before they can be weaponized.
  • Provides concrete evidence of a control gap in patch management that can be captured in a Trust Center audit package.
  • Demonstrates the need for continuous inventory and automated version‑checking to satisfy control‑objective monitoring across frameworks.

Who is affected

TECH_SAAS

Recommended actions

  1. Run an inventory scan to locate all NGINX instances with HTTP/2 enabled.
  2. Upgrade to NGINX 1.31.9 (mainline) or 1.30.7 (stable) without delay.
  3. If upgrade is not possible, disable HTTP/2 in the configuration as a temporary mitigation.
  4. Validate the patch via binary analysis or version check and record the evidence for audit readiness.
  5. Enable logging of HTTP/2 frame anomalies and monitor for suspicious process activity.

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.