Java4Shell (CVE-2026-114938) Patched: OpenAI's Codex Found the Java RCE in an Hour, but the Bug Sat in a Public Tracker Since June — Who Is Really Exposed and How to Fix It

AI · 2026-11-20 · By H.A

Java4Shell (CVE-2026-114938) Patched: OpenAI's Codex Found the Java RCE in an Hour, but the Bug Sat in a Public Tracker Since June — Who Is Really Exposed and How to Fix It

Oracle and OpenJDK have fixed Java4Shell, a Base64 decoder overflow that allows pre-auth RCE in Keycloak, Jenkins, Jira and more on AVX-512 VBMI servers, after an AI agent rediscovered a crash first reported publicly in June.

Oracle and the OpenJDK project have shipped fixes for Java4Shell (CVE-2026-114938), a memory-corruption flaw in the Java Virtual Machine's Base64 decoder. When we covered it on 17 November it was still a reserved CVE with no advisory. Since then the fixes are out, CISA has told organisations to patch immediately, and the discoverers' timeline has turned up something odd: the bug was not new. A user had reported the crash publicly in June. An AI coding agent then found it again in under an hour in October, and that rediscovery, backed by working exploits, is what got it fixed.

This piece covers what changed since the CVE went public, which systems are actually exposed (fewer than the "Log4Shell" comparisons suggest), and what to do before the product-specific exploits come out.

What Happened

Oracle and OpenJDK released the fixes at 01:00 Mauritius time on 18 November (21:00 UTC on 17 November). Security firm Calif, which reported the flaw to Oracle, published its write-up minutes later and named the bug Java4Shell. CISA issued an alert the same day. It urged organisations to find every affected Java installation, including runtimes bundled inside third-party applications, container images and appliances, and to patch internet-facing systems first.

Calif says it has demonstrated pre-authentication remote code execution against default configurations of Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate. It also reports post-authentication RCE in Kafka, Solr, Elasticsearch, Gerrit and Spinnaker. The firm is holding back those product-specific exploit chains until users have had time to upgrade, and says it will publish them later. Its public proof of concept only reproduces the memory corruption.

The AI Angle: Found in an Hour, but Reported in June

According to Calif's timeline, researcher Quang Luong told OpenAI's Codex agent to audit HotSpot's JIT compiler, intrinsics and cryptography code. Codex flagged the bug within an hour on 24 October. Calif says a first working exploit took about two more hours and less than $200 in model costs, and that the transcripts show the agent did not look up existing bug reports.

Two days later Calif found that the bug was already public:

Calif's own conclusion is that the bug "was actually public" and was fixed only once someone showed it could be exploited. For defenders this is the part that matters. Crash reports that look like reliability bugs can hide security flaws for months. AI agents can now go through that backlog, and turn a crash into an exploit, faster and more cheaply than many triage teams can.

Technical Details

The flaw is in HotSpot's hand-written x86-64 Base64 intrinsic: optimised machine code the JVM uses in place of the Java implementation of java.util.Base64.Decoder. On CPUs with AVX-512 VBMI, the JVM picks a vector routine that decodes 64 bytes at a time. Calif found that the store mask for the padded tail is calculated wrongly. With = padding the output length underflows, the mask becomes all ones, and 64 bytes are written at offset 48 of a 50-byte buffer, 62 bytes past its end. Java then rejects the malformed input, but by that point memory has already been corrupted.

Things to know about exploitability:

Who Is Affected

All three of these must be true:

Red Hat calls affected systems "vulnerable out of the box", because the JVM selects the AVX-512 path automatically.

Patch Status

Oracle rates the flaw 8.1 under CVSS 3.1, citing high attack complexity. Calif scores it 9.2 (Critical) under CVSS 4.0, and Red Hat rates it Critical. Oracle's fixed builds are 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. Amazon Corretto, Azul Zulu, Oracle GraalVM and Eclipse Temurin have published matching builds. Distribution packages are uneven. As of its 20 November update, Red Hat says it is still expediting errata for RHEL 8, 9 and 10, and Debian had fixed only its unstable branch. The Keycloak project has shipped updated images.

Restart services after patching. A running JVM keeps the vulnerable code until it is restarted.

As of 19 November, no exploitation in the wild had been confirmed, and the CVE was not in CISA's Known Exploited Vulnerabilities catalog. Internet-scanning researchers have logged a small number of Java4Shell-shaped probes from a handful of IP addresses, with no successful intrusions reported.

What To Do Now

# Does this CPU have the vulnerable feature set? (all four must print)
grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'

# Java version
java -version 2>&1 | head -1

# Interim mitigation until the fixed build is installed
export JAVA_TOOL_OPTIONS="${JAVA_TOOL_OPTIONS:+$JAVA_TOOL_OPTIONS }-XX:-UseBASE64Intrinsics"

# Confirm a running JVM picked it up (expect: bool UseBASE64Intrinsics = false)
jcmd <pid> VM.flags -all | grep -F UseBASE64Intrinsics

Why It Matters

Java4Shell is unlikely to be a repeat of Log4Shell. The CPU requirement, JIT warm-up and ASLR bypass narrow it considerably, and several researchers do not expect mass exploitation. The risk will go up once Calif publishes its product chains, though, and denial of service is already easy for anyone who can reach an exposed decoder. The bigger lesson is in the timeline. A security bug sat in a public tracker for four months, with a proposed fix that was closed unmerged, until an AI agent rediscovered it and a human team proved it was exploitable. Attackers have the same agents, and public crash reports are now material for exploits.

Sources

COMPUTE NODE · · --:--:--

Fresh cybersecurity news,
daily threat intelligence.

Daily cyber news, live threat intel and exploited CVEs.

Everything in one place

Self-hosted, hardened, and yours.

RUN IT

Local AI console

Chat with a model on your own hardware via Ollama or any OpenAI-compatible server. No cloud, no key.

DEFEND

Cyber threat feed

Automatic daily intel from CISA KEV, NVD & GitHub advisories, a live cyber threat map, and your own notes.

NEWS

News & videos

Articles and updates on pentesting, AI, and cyber — with embedded video, including YouTube. Post your own.

DIRECTORY

Registry

Runtimes, models, MCP servers, agents, and a full security & pentest tooling section.

PUBLISH

Posts

Write, edit, publish, and share articles backed by a real database and your account.

COMMUNITY

Forum

Threads and replies across categories from Models to Hardware to Security.

CODE

Repos

Curated AI and security GitHub repos, plus a shelf for pinning your own.

DOWNLOAD

Skill packs

Agent starters, RAG scaffolds, and defensive security & VAPT report templates.

Registry

Runtimes, models, MCP servers, agent frameworks, and a security & pentest tooling section — all links out to the real projects.

Local AI console

Talk to a model running on your own machine through Ollama or an OpenAI-compatible server — your prompts and the model's replies always go straight from your browser to your local model, never through a Reef server. Attach files for context, and pick up saved chats where you left off.

Type /image a prompt in the box below to generate
Not connected

Local AI hardware benchmark

A spec-based compatibility advisor — tells you which local models your hardware can run well, which will be slow, and which to skip. Connect to Ollama below for a real, measured speed test instead of an estimate.

1. Your hardware

2. Live check against your local model server (optional)

If a local model server is running, this cross-references the table above with what you've actually got loaded — and runs a real, measured speed test instead of an estimate.

AI Database

A browsable catalog of AI models across providers — context windows, pricing, and capabilities.

Loading…

Cyber threat feed

Latest threats pulled automatically every day from CISA's Known-Exploited-Vulnerabilities catalog and NVD — plus threat intel you post yourself.

⇩ Export STIX
Loading threat feed…

Cyber threat map

Attacks happening right now, all over the world.

Connecting…
LIVE · MAURITIUS TIME--:--:--
attack route, country to country attack route into Mauritius attacker reported worldwide
Loading live data…
attackers reported per minute · click to rewindnow

Top attack routesweb

Attackers based inlast hour

Networkslast hour

Click any dot, feed row or table row to see that IP's profile.

Mauritius

Who attacks Mauritius

Loading…

Web attacks malicious requests to Mauritian websites that were blocked
Network DDoS floods meant to knock Mauritian servers offline

    Mauritius · last 24 h

    How Mauritius is attacked

    Network-level attacks (DDoS) aimed at Mauritius, by method. They try to knock servers and networks offline by sheer volume.

    • Loading…

    The ports or services these floods aimed at aren't published.

    Mauritius · last hour

    Attackers located in Mauritius

    0attackers located in Mauritius were reported in the last hour

    This counts attacks coming from Mauritius, not attacks on it: IPs in Mauritius that servers elsewhere reported for attacking them. Usually zero or one; when it rises, it's often a hacked local server or router.

    Worldwide today

    What attackers are knocking on

    Ports most targeted across a worldwide network of sensors .

    Worldwide today

    Most active attackers

    Ranked by how many separate sensors they hit. Click a row for its profile.

    IPCountryNetworkSensors hitReports
    What you're looking at
    Blue routes

    Share of attack traffic from one country to another. Thicker, faster streams carry more. Particles show volume, not one per attack.

    Every 15 min · published 1–2 h behind
    Amber flashes

    An attacking IP that servers around the world reported in the last minute, placed where the IP is. Its targets aren't published, so there's no line.

    Every minute · shown about 1 min behind
    Locations

    IP locations are approximate (city level at best) and show where the machine is hosted, not who controls it.

    Approximate · city level at best

    News

    Articles, guides and updates on pentesting, AI, and cybersecurity — with embedded video. Add your own, including YouTube.

    Loading…

    Posts

    Loading…

    Loading posts…

    Forum

    Questions, answers, and talk about running AI locally.

    Loading forum…

    GitHub repositories

    Curated AI and security repos, plus your own pinned shelf.

    Command board

    One-liners, configs, and advice worth keeping — shared by everyone here.

    ⚠ Commands are shared with all users. Never include credentials, tokens, or internal hostnames. Review anything before you run it.
    Loading commands…

    Skill packs

    Starter files served from the API — AI agent scaffolds plus defensive security & VAPT reporting templates. Click to download.

    Loading skills…

    Your watchlist

    Follow threat actors, malware, CVEs and vendors — we tell you when a new report, CVE record or exploitation alert mentions them.

    Threat Library

    Threat actors, malware and tools — their attack techniques, Reef Sentinel coverage and indicators of compromise.

    Loading…

    Threat Intelligence

    Curated threat write-ups, advisories and analysis — with cover media.

    Loading…

    Tutorials

    Step-by-step guides for running local AI, using the console, and tracking threats. Admins can add their own.

    Loading…

    Downloads

    Direct links to the official homepage/download page for well-known cybersecurity, penetration-testing, and local-AI software. Always verify checksums/signatures from the vendor before running anything.

    Loading…

    Privacy Policy

    Loading…

    Terms & Conditions

    Loading…

    Help & FAQ

    Answers to common questions about Reef Sentinel, plus a formatting guide for posts, articles, and comments.


    Formatting guide

    Commands you can type into the body of a post, comment, or reply — no HTML needed. Comments and short replies only support bold, italic, and inline code.

    Contact us

    Questions, feedback, or a security disclosure? Reach us directly, or send a message and we'll get back to you by email.

    Loading…

    Send a message

    VAPT Report Generator

    Build an engagement, add findings with a live CVSS calculator, and generate a branded, print-ready report.

    Recon Toolkit

    Investigate any domain, IP, URL, file hash, email or CVE in one search, plus breach and password checks, hash identification and a payload cheatsheet.

    Outage Monitor

    Is Microsoft 365, Facebook, Google, AWS or ChatGPT down? Live status of the big tech services from their official status pages, every incident with its full timeline, and how long each one took to fix.

    Website Checker

    Reads a website's HTTP response headers to identify its framework and server, shows any known CVEs for the exposed versions with details, and recommends what to do.

    Control panel

    Manage everything shown on the site — news & videos, posts, homepage headlines, and subscribers. Admin only.

    Overview
    Content
    Site
    Account & Security

    Email settings

    SMTP on ports 25/465/587 is blocked outbound by some hosts (e.g. DigitalOcean droplets by default) — Resend and Brevo send over their HTTPS API instead, so they work even then. Only the selected provider is used to send; the others stay saved but idle, so you can switch back any time without losing settings.

    Get a key from resend.com/api-keys. Uses the "From address" below as the sender — it must be on a domain you've verified with Resend.

    Get an API key (not an SMTP key) from app.brevo.com/settings/keys/api. Uses the "From address" below as the sender — it must be a verified sender in your Brevo account.

    "From address" and "Site name/URL" are shared by SMTP, Resend, and Brevo — they control what recipients see, regardless of which provider is active.

    Send a test email

    Sends through whichever provider is currently active above. Save your settings first if you just changed them.

    SIGNAL LOST

    We couldn't find this page

    The page may have been moved or deleted, or the address was mistyped.