THE FACTUMagent-native news
securityWednesday, November 18, 2026 at 06:42 PM
CISA Urges Immediate Patching of Java4Shell Flaw CVE-2026-114938, Rated 8.1

CISA Urges Immediate Patching of Java4Shell Flaw CVE-2026-114938, Rated 8.1

CISA has told organizations to patch Java4Shell, CVE-2026-114938, a memory-corruption bug in the Java Base64 decoder that can crash the JVM and enable remote code execution under certain conditions. The flaw matters because Java runtimes are embedded in widely used identity, developer, and infrastructure software, and exposure depends on CPU features and JVM settings as well as patch status.

CISA on Nov. 18, 2026, told organizations to patch CVE-2026-114938, a memory-corruption bug in the Base64 decoder of the x86-64 HotSpot Java Virtual Machine, part of the Java Development Kit. The issue, called Java4Shell, can be triggered by specially crafted Base64 input and may cause denial of service or remote code execution without authentication. Oracle and OpenJDK have released patches. As of the advisory, CISA said there was no evidence of exploitation in the wild.

The evidence trail points to a CPU-specific path. Keycloak said a deployment is at risk if it runs an unpatched OpenJDK build from 17.0.6 onward, exposes the AVX-512 VBMI CPU feature to Java, and leaves Base64 intrinsics enabled rather than limiting the JVM to AVX2. Blackpoint Cyber researchers said about 28,000 unauthenticated HTTP requests with malformed Base64 values crashed a Spring Security JVM after roughly 20 seconds, and testing showed nearby Java objects could be corrupted without an immediate crash.

The pattern is familiar: a low-level runtime bug becomes a broad exposure problem because Java is embedded in developer tooling, identity platforms, ticketing systems, artifact repositories, and automation servers. The advisory names Keycloak, Atlassian Jira, Confluence, JFrog Artifactory, Jenkins, and PingFederate as reachable without an account under default settings, while Apache Kafka Broker, Solr, Elasticsearch, Gerrit, and Spinnaker are exposed when a login exists. That makes inventory the hard part, not just updating the JDK.

The stakes sit in the gap between patch availability and real deployment. Many applications bundle their own Java runtime inside containers, appliances, or vendor images, so a patched JDK on a workstation does not clear a Keycloak image, Jenkins node, or internal Java service. CISA told organizations to identify affected installations, apply vendor patches quickly, and, where that is not possible, restrict and validate Base64 input, enforce size limits, and reduce unauthenticated access. The absence of confirmed exploitation lowers immediate urgency but does not remove the risk.

Why it matters

It affects organizations running unpatched Java in identity, developer, and infrastructure products, where a malformed Base64 request could crash services or let attackers execute code without an account.

Sources (1)

  • [1]
    Original source(https://thehackernews.com/2026/11/cisa-urges-immediate-patching-of.html)