Java4Shell: RCE in OpenJDK when processing Base64
- ID
- 47611
- Status
- summarized
- Published
- 18 Nov 2026, 5:11 AM
- Fetched
- 18 Nov 2026, 8:04 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://calif.io/java4shell/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 8.5
- Created
- 18 Nov 2026, 8:04 AM
- Tags
- Audience
- developerssaas_startup_founders
What happened
Calif Research disclosed CVE-2026-114938 ('Java4Shell'), a memory-corruption bug in OpenJDK's optimized x86-64 Base64 decoder that scores 9.2 CRITICAL under CVSS 4.0 and is triggered by 64 'A' characters followed by a single '=' (128 'A' plus '=' on OpenJDK 17). The write-up claims demonstrated pre-auth RCE in Keycloak, Atlassian Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate, post-auth RCE in Kafka, Solr, Elasticsearch, Gerrit and Spinnaker, plus a client-side case where a Java program opening a TLS connection to a malicious server is compromised. The excerpt names no patched version, release date, or mitigation.
Why it matters
The pre-auth label is the actionable part: for Jenkins, Keycloak, Confluence, Jira and Artifactory in default configs, the vulnerable Base64 decoder is reached before login, so your network exposure decides risk rather than user roles — an internet-facing Jenkins is a different decision from an internal one. Because the write-up gives no fixed build, the practical step this week is inventorying which JDK build each service actually runs (the trigger differs between OpenJDK 17 and newer) and identifying which of your endpoints decode Base64 pre-auth, including auth headers and file uploads, since you cannot yet patch to a named version.
Discussion angle
Java sells memory safety, yet this bug lives in the vectorized intrinsic that bypasses it — worth asking the room whether anyone can actually name the JDK build and patch level behind their Jenkins, Keycloak or Elasticsearch instances today.