Live threats
HighFive Critical nginx Vulnerabilities (nginx2root) Expose Millions of Web Servers – Cloudflare Proxy Mitigates Most BreachJPMorgan, Visa & Mastercard Elite Cardholder Data Exposed in Third‑Party Marketing Vendor Hack Rule changeHHS finalizes HIPAA Privacy Rule changes, cutting access request deadline to 15 days DeadlineFCC finalizes rule letting consumers revoke consent for specific robocall categories CriticalCritical Java4Shell (CVE‑2026‑114938) Heap‑Corruption Vulnerability Threatens Java Applications; Cloudflare Adds WAF Rules BreachAttackers Inject Malicious JavaScript via Optimizely, Compromising 178 High‑Profile Websites Rule changeCNIL and Groupe VYV publish "La Voix des jeunesses" report on youth conversational AI use CriticalRemote Code Execution Vulnerabilities Found in Brazil’s Government‑Approved E‑Signature Middleware
Updated 09:09 UTC All intelligence →
BREACH WATCH BRIEF High ☁️ Vulnerability

Five Critical nginx Vulnerabilities (nginx2root) Expose Millions of Web Servers – Cloudflare Proxy Mitigates Most

Ten nginx flaws were disclosed, five of which (nginx2root) allow unauthenticated code execution and root escalation. Cloudflare’s edge proxy blocks the most dangerous HTTP/2/HTTP/3 attack vectors, giving operators time to patch. This underscores the need for third‑party risk controls that limit direct exposure of critical assets.

SeverityHigh
Type☁️ Vulnerability
ConfidenceHigh
ReportedNov 20, 2026
Technology & SaaS SaaS providers E‑commerce platforms Media and content delivery sites Any organization exposing nginx to the internet Vulnerability Exploit

What happened

F5 and nginx.org announced ten vulnerabilities; five memory‑corruption bugs (nginx2root) can be triggered via crafted HTTP/2/HTTP/3 frames, and a Linux kernel bug can elevate privileges to root. Scans show ~8.8 M nginx servers with HTTP/2 enabled are potentially vulnerable. Cloudflare’s proxy terminates these protocols, preventing the exploit from reaching the origin.

Why it matters for trust and compliance

  • The case illustrates the control objective of protecting external attack surfaces through vetted third‑party services; using a CDN proxy provides immediate mitigation while organizations address underlying configuration and patch gaps.
  • Demonstrates the value of continuous third‑party monitoring as evidence for audit readiness.
  • Supports control mapping for perimeter protection and supply‑chain risk management.

Who is affected

SaaS providers E‑commerce platforms Media and content delivery sites Any organization exposing nginx to the internet

Recommended actions

  1. Run an inventory of all nginx deployments and verify version and feature usage.
  2. Patch to nginx 1.30.7 / 1.31.9 (or vendor‑provided equivalents) and restart services.
  3. Restrict origin access to Cloudflare‑only paths (Tunnel, IP allow‑list, Authenticated Origin Pulls).
  4. Disable unused HTTP/2, HTTP/3, resolver, and mail proxy features if patching cannot be applied immediately.

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.