# SZB-4ac46a182e: 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.

- Type: Early warning
- Kind: Pending CVE
- Vendor: OpenJDK
- Product: OpenJDK
- Status: Corroborated
- Sources: 4 distinct
- First seen: 2026-11-17 21:56 UTC

> No statement or filing from OpenJDK has reached cve.now yet. Every claim below is quoted from, and linked to, the source that made it.

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

## 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

- 2026-11-17 21:55 UTC: Made public by Catalin Cimpanu on Bluesky
- 2026-11-17 21:56 UTC: First seen by cve.now
- 2026-11-18 00:00 UTC: Record last updated

## Evidence (4 sources)

- 2026-11-17 · Press · [Catalin Cimpanu on Bluesky](https://bsky.app/profile/campuscodi.risky.biz/post/3n2jztkr2ts23): “A memory-corruption vulnerability in OpenJDK's Base64 decoder.”
- 2026-11-17 · Social · [Mastodon](https://infosec.exchange/@censys/117634278507700588): “Java4Shell (CVE-2026-114938) could enable remote code execution and memory disclosure in affected OpenJDK installations.”
- 2026-11-17 · Press · [BleepingComputer on Bluesky](https://bsky.app/profile/bleepingcomputer.com/post/3n2k5pv6s262e): “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.”
- 2026-11-17 · Social · [oss-security](https://seclists.org/oss-sec/2026/q4/757): “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: https://github.com/sazabi/cve.now/issues/new?title=Wrong%20fact%20on%20SZB-4ac46a182e&body=https%3A%2F%2Fcve.now%2FSZB-4ac46a182e%0A%0AWhat%20is%20wrong%2C%20and%20the%20source%20that%20shows%20it%3A%0A

## 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: https://bsky.app/profile/campuscodi.risky.biz/post/3n2jztkr2ts23, https://infosec.exchange/@censys/117634278507700588, https://bsky.app/profile/bleepingcomputer.com/post/3n2k5pv6s262e, https://seclists.org/oss-sec/2026/q4/757

### 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.

## Related

- Browse: [Early warnings](https://cve.now/early-warnings.md)

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/SZB-4ac46a182e
Site guide for agents: https://cve.now/llms.txt
