English edition · cyberattaques.org in FrenchFrançais
VulnerabilityPatch available

CISA urges immediate patching of 'Java4Shell' flaw in HotSpot JVM Base64 decoder

CISA is urging organisations to patch CVE-2026-114938 now, a memory-corruption flaw in the x86-64 HotSpot JVM Base64 decoder that can lead to unauthenticated remote code execution. Any organisation running JDKs or Java runtimes, including those bundled inside third-party software, is concerned.

What to do now Illustration photo (software code)
CVSS severity8.1High
EPSS probability1 %
ExploitationNot observed
PatchAvailable
Product
Oracle Java (HotSpot JVM x86-64, JDK)
Affected versions
Not stated in the source; see Oracle's November 2026 security advisory.
Fixed in
Not stated; fixes are in Oracle's November 2026 Critical Security Patch Update.
CVE
CVE-2026-114938

On 17 November 2026, the US Cybersecurity and Infrastructure Security Agency (CISA) issued an alert telling organisations to patch CVE-2026-114938 immediately. The critical Java vulnerability, nicknamed 'Java4Shell', is addressed in Oracle's Critical Security Patch Update for November 2026.

The bug sits in the Base64 decoder of the HotSpot Java Virtual Machine on x86-64, which ships as part of the Java Development Kit. It is a memory-corruption issue: crafted Base64 input can crash the JVM and, according to CISA, may let an unauthenticated attacker run code remotely.

CISA's alert does not list affected or fixed versions and points readers to Oracle's advisory for those details. It also does not say whether the flaw is being exploited.

Finding every exposed instance is likely to be the hardest part. CISA notes that JDKs and Java runtimes are frequently bundled with third-party applications, container images and appliances, and may not show up as separate items in software inventories. Fixes from those vendors may follow Oracle's own release.

Where patching cannot happen right away, CISA suggests temporary compensating controls: restricting and validating Base64 input at the application boundary, enforcing input-size limits and cutting back unauthenticated access.

Action plan

What to do now

  1. Inventory every Java installation, including runtimes bundled in third-party applications, container images and appliances.
  2. Apply Oracle's Java patches and any vendor updates as soon as they are available, starting with internet-facing systems.
  3. Check Oracle's November 2026 Critical Security Patch Update advisory to confirm which products and versions are affected.
  4. If you cannot patch yet, validate and restrict Base64 input at the application boundary, enforce input-size limits and limit unauthenticated access.
  5. Monitor for unexpected JVM crashes, suspicious Java processes and rogue runtimes.

Sources