Live threats
CriticalCritical Java4Shell (CVE‑2026‑114938) Enables Unauthenticated RCE on AVX‑512‑Enabled OpenJDK 17+ 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 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:39 UTC All intelligence →
BREACH WATCH BRIEF Critical 🐛 Vulnerability

Critical Java4Shell (CVE‑2026‑114938) Enables Unauthenticated RCE on AVX‑512‑Enabled OpenJDK 17+

Cisco Talos disclosed Java4Shell (CVE‑2026‑114938), a critical unauthenticated RCE flaw in OpenJDK 17.0.6+ on AVX‑512‑enabled x86‑64 CPUs. The large attack surface makes timely patching a control‑assurance priority for any organization running Java workloads.

SeverityCritical
Type🐛 Vulnerability
ConfidenceHigh
ReportedNov 19, 2026
Cloud & Infrastructure Providers Technology & SaaS providers Cloud infrastructure operators Enterprises with Java workloads on modern x86‑64 hardware Vulnerability Exploit

What happened

Talos reported a new CVE‑2026‑114938 vulnerability in OpenJDK 17.0.6 and later that allows unauthenticated remote code execution when a malformed Base64 payload reaches the JVM on CPUs with AVX‑512 VBMI. Lab exploits have succeeded, but no wild activity is known. The flaw affects on‑prem and cloud systems that run Java on modern Intel or AMD processors.

Why it matters for trust and compliance

  • The issue underscores the need for robust vulnerability‑management controls—identifying, prioritizing, and remediating critical flaws promptly to satisfy audit requirements across frameworks.
  • Demonstrates the necessity of continuous vulnerability monitoring and evidence of timely patching.
  • Provides a concrete control‑mapping example that supports audit readiness across multiple frameworks.

Who is affected

Technology & SaaS providers Cloud infrastructure operators Enterprises with Java workloads on modern x86‑64 hardware

Recommended actions

  1. Inventory Java runtimes and locate OpenJDK 17.0.6+ on AVX‑512 CPUs.
  2. Apply the latest OpenJDK patches immediately; if delayed, disable AVX‑512 with -XX:UseAVX=2.
  3. Deploy Talos Snort rules and enable Splunk detections for malformed Base64 traffic.
  4. Integrate CVE‑2026‑114938 into your continuous monitoring and map remediation evidence to your control framework.

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.