A memory corruption bug in Oracle's Java can let an attacker run their own code on a server without a username, a password or any prior access, and the US Cybersecurity and Infrastructure Security Agency has told organisations to patch it immediately. The flaw is tracked as CVE-2026-114938 and has picked up the nickname Java4Shell, a pointed reference to the Log4Shell flaw that forced emergency patching across the industry in 2021.

The trigger is Base64, the encoding Java uses constantly to move login credentials and uploaded files between systems. When the runtime decodes certain input, memory is corrupted in a way that hands control to the attacker. Oracle scored the flaw 8.1 out of 10 on the standard severity scale, which places it below the maximum but well inside the range that security teams treat as an emergency.

Who found it, and when

Thai Duong, chief executive of the security firm Calif, told CNET that his company identified the bug in October and reported it to Oracle, which has since shipped a patch. CISA followed with guidance telling organisations to inventory their Java installations and apply vendor fixes as soon as they are available.

The exposure is broad because Java sits under enterprise software rather than on phones. Federico Kirschbaum, who leads the Security Lab at the security company XBOW, told CNET that the runtime's footprint reaches finance, government, transport and large corporations, often inside applications that a company bought years ago and no longer inspects. Kirschbaum called Java "a great language for creating solutions," then added that the bug is a reminder that the languages teams build on carry flaws, and that everything built on top can inherit them.

The patch is the easy part

Finding affected systems is slower. Java runtimes accumulate: one for the application server, one bundled inside a log pipeline, one an old build left behind on a virtual machine. CISA's advice to review software inventories for JDKs and runtimes assumes an organisation knows what it is running, which is often the weakest link in exactly the sectors Kirschbaum named.

The timing adds pressure. The same week brought a string of outages at Apple, banks and air traffic systems that officials attributed to ordinary software failure rather than an intruder, and the volume of vulnerability reports reaching maintainers has been rising faster than the people who review the fixes. Finding a bug is now the cheap part of the job; deciding what to do about thousands of them is not.

Why the name will stick

Security nicknames are marketing, and this one is doing work: it tells an IT manager in one word that the bug is remotely reachable, widely installed and worth a weekend. The comparison to Log4Shell also sets an expectation about the next few weeks, when scanners start probing for unpatched Base64 endpoints and proof-of-concept code circulates.

Kirschbaum's own framing is that this is the normal state of the stack rather than an exception. "That new normal is that most of the technology we rely on has flaws, and now that we have resources using LLMs, we can find those problems," he said, adding that attackers have the same tools. "We are in a race to find the problems first and help the industry by guiding them on what's urgent so they patch it." For anyone running a Java service, the race this week is a version check.