Skip to main content
Menu
Early warnings

Early warning

Java4shell: details published for OpenJDK Base64 decoder memory-corruption flaw

Details of a memory-corruption vulnerability in OpenJDK's Base64 decoder have been published, as reported by Catalin Cimpanu. The item says a remote attacker with no credentials can overwrite heap memory and reach remote code execution.

SZB-4ac46a182ePending CVECorroborated

Written by a model from the sources below. Verify against them.

Sources4Corroborated
Kind
Pending CVE
Vendor
OpenJDK
Product
OpenJDK
Status
Corroborated
First seen

What to do

  • Update OpenJDK to a patched release as soon as one is available.

  • Review applications that decode untrusted Base64 input until patched.

  • Check the published write-up to confirm which OpenJDK versions are affected.

  • Apply vendor patches for Jenkins, Jira, Confluence and Keycloak.

  • Restrict network access to these services until they are patched.

Timeline

  1. Made public by Catalin Cimpanu on Bluesky
  2. First seen by cve.now1 day
  3. Record last updated

Evidence 4

  1. Press
    Catalin Cimpanu on Bluesky
    “A memory-corruption vulnerability in OpenJDK's Base64 decoder.”
  2. Social
    Mastodon
    “Java4Shell (CVE-2026-114938) could enable remote code execution and memory disclosure in affected OpenJDK installations.”
  3. Press
    BleepingComputer on Bluesky
    “A critical vulnerability dubbed Java4Shell in OpenJDK, the open-source implementation of Java, can allow unauthenticated attackers to remotely execute code on popular enterprise applications, including Jenkins, Atlassian Jira, Confluence, and Keycloak.”
  4. Social
    oss-security
    “CVE-2026-114938: OpenJDK pre-auth RCE via memory-corruption in Base64 decoder”

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about SZB-4ac46a182e

Has OpenJDK confirmed it?

Catalin Cimpanu on Bluesky, Mastodon and BleepingComputer on Bluesky report it. No statement from OpenJDK has reached cve.now yet.Source: Catalin Cimpanu on Bluesky, Mastodon, BleepingComputer on Bluesky, oss-security

What should OpenJDK and Jenkins users do?

Update OpenJDK to a patched release as soon as one is available. Review applications that decode untrusted Base64 input until patched. Check the published write-up to confirm which OpenJDK versions are affected. Apply vendor patches for Jenkins, Jira, Confluence and Keycloak. Restrict network access to these services until they are patched.