SAASMENT

News

CISA says patch Java4Shell before crafted Base64 input hits the JVM.

CISA told organizations to patch CVE-2026-114938 now: a Base64 decoder bug in the x86-64 HotSpot JVM that can crash Java or lead to unauthenticated code execution.

Illustration of a cracked runtime memory bar beside a patch shield

Impact

What was impacted
The Base64 decoder in the x86-64 HotSpot JVM (CVE-2026-114938, CVSS 8.1), called Java4Shell. Crafted Base64 input can crash the JVM or, under some conditions, allow unauthenticated remote code execution. Oracle and OpenJDK have shipped patches. CISA says there is no evidence of exploitation in the wild yet.
Who was impacted
Teams running Java services that decode Base64 before login, including Keycloak, Jira, Confluence, Artifactory, Jenkins, and PingFederate under default settings. Also Kafka Broker, Solr, Elasticsearch, Gerrit, and Spinnaker, where a login is required. Include JDKs bundled inside third-party apps, containers, and appliances.
What you need to do
Inventory every JDK and Java runtime, including copies hidden in apps and images, and apply the Oracle, OpenJDK, and vendor patches. If you cannot patch immediately, validate Base64 at the application boundary, cap input size, and limit unauthenticated access.

CISA urged organizations to patch Java4Shell (CVE-2026-114938) immediately. It is an out-of-bounds write in the Base64 decoder of the x86-64 HotSpot JVM, which ships in the JDK. Specially crafted Base64 can crash the process and, in some cases, let an attacker run code without an account.

Oracle and OpenJDK have published fixes. At the time of the alert, CISA had no evidence the flaw was being exploited. Researchers have still shown it is reachable on common products: without a login on Keycloak, Jira, Confluence, Artifactory, Jenkins, and PingFederate, and after a login on Kafka Broker, Solr, Elasticsearch, Gerrit, and Spinnaker, under default settings.

Blackpoint Cyber described a local Spring Boot app using Spring Security. About 28,000 unauthenticated HTTP requests carrying a malformed Base64 authentication value terminated the JVM after roughly 20 seconds. Further tests corrupted nearby Java objects and changed live application data without always causing a crash.

CISA’s sequence is to find every affected Java install, including runtimes bundled in third-party software, container images, and appliances, then apply Java and vendor patches as they ship. Until a patch is in place, restrict and validate Base64 input at the edge, enforce size limits, and reduce unauthenticated exposure.

For your AI agent

Agent instructions — copy paste to Claude

You are helping me respond to CISA’s call to patch Java4Shell (CVE-2026-114938, CVSS 8.1). It is an out-of-bounds write in the Base64 decoder of the x86-64 HotSpot JVM. Crafted Base64 input can crash the JVM and, under some conditions, allow unauthenticated remote code execution. Oracle and OpenJDK have released patches. CISA reported no evidence of in-the-wild exploitation at the time of the alert.

Context:
- What was impacted: Base64 decoding in the x86-64 HotSpot JVM. Unauthenticated reachability has been reported under default settings on Keycloak, Jira, Confluence, Artifactory, Jenkins, and PingFederate. Authenticated reachability has been reported on Kafka Broker, Solr, Elasticsearch, Gerrit, and Spinnaker.
- Who should care: operators of those apps and anyone shipping a JDK inside an application, container, or appliance.
- Fix: apply Oracle, OpenJDK, and vendor Java patches. If patching is delayed, validate and size-limit Base64 at the application boundary and limit unauthenticated access.

Do this in order. Ask before restarting production services or changing edge rules. Prefer inventory first. Do not attempt exploit proofs of concept.

1. Inventory
   - Find Java processes, container images, and appliances. Record vendor, version, and whether the runtime is bundled inside another product.
   - Flag internet-facing services that decode Base64 (Basic auth, tokens, or similar) before login, especially the products listed above.
2. Contain
   - Where a patch is not ready, propose compensating controls: reject or strictly validate Base64 at the edge, enforce input-size limits, and restrict unauthenticated access. Ask before applying them.
3. Remediate
   - Plan installation of the fixed JDK or the vendor patch, then restart services and rebuild images so the running process picks up the new runtime.
4. Verify
   - Confirm the running Java version and image digest after the change. Note any product still waiting on a vendor build.
5. Report back
   - Inventory, what was patched, what is still exposed, compensating controls in place, and residual risk.

Do not invent CVE details, version numbers, or JVM flags beyond what I provided. If a check needs access I have not given you, say what you need and stop.

← All news

Try the platform.

Open the demo workspace with mock data. No login. Register from the banner when you want early access. No security team. No call.

Try the platform