A Base64 bug has been shown against Keycloak and PingFederate defaults, which confirms that identity servers will open any parcel before asking who sent it.
Java4Shell (CVE-2026-114938) is a memory-corruption flaw in OpenJDK’s Base64 decoder, reachable on x86-64 chips with AVX-512 VBMI in OpenJDK 17.0.6 or newer. Calif, who disclosed it, says it achieved remote code execution in default configurations of Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate, and scores it 9.2 under CVSS 4.0. Oracle and OpenJDK patched on 17 November.
The identity twist: servers decode Base64 from Basic headers, SAML artifacts and CSRF tokens before checking the login, so The Hacker News reads the attacks as needing none. The bouncer inspects your coat before checking the guest list.
Calif is withholding its exploits, other labs reproduced crashes and a memory leak but not code execution, and Canada’s Cyber Center knew of no attacks. I found no statement from Keycloak or Ping. Ory says it is unaffected, being Go and TypeScript with no JVM, a serenity it is clearly enjoying.
Patch the JDKs under your IdP and CI first; Calif says ARM64 is unaffected. “Researchers are holding back exploit code” has a shelf life.
Sources: Calif · The Hacker News · Ory