Tech Translated

IT Security & Technology Blog

Practical IT insights for Australian businesses. Our team covers cybersecurity advisories, compliance updates, and plain-English explainers on the technology your business relies on, published regularly as the landscape shifts.

Java4Shell CVE-2026-114938 security advisory, All IT Services

Java4Shell (CVE-2026-114938): Patch Oracle Java and OpenJDK Now

A newly disclosed flaw in Java, nicknamed Java4Shell, could let an unauthenticated attacker run code on your systems. There is no known exploitation yet, but CISA wants it patched now, and so do we.

Security researchers at Calif disclosed CVE-2026-114938, a memory corruption bug in Java's Base64 decoder that can lead to remote code execution. It affects Oracle Java SE, Oracle GraalVM and OpenJDK builds, and has already been demonstrated against default installs of common business tools like Keycloak, Jira, Confluence, Jenkins, JFrog Artifactory and PingFederate. Oracle pushed fixed builds on 17 November 2026, and CISA is urging organisations to patch immediately.

Why this matters for Australian businesses

Here is the part most owners miss. You might be certain you do not run Java, but Java is quietly bundled inside a surprising amount of business software. Across our Central West NSW and Sydney Northern Beaches client environments, we regularly find Java runtimes tucked inside line-of-business apps, print and label systems, backup consoles and developer tools, often without anyone realising they are there. The flaw is rated difficult to exploit and there is no universal exploit, so this is not a drop everything panic. But an internet-facing Java service, especially an admin portal, is exactly where you do not want an unpatched memory bug sitting while attackers reverse engineer the fix.

What to do about Java4Shell

  • Inventory every Java runtime. Include the copies bundled inside other apps, not just the standalone installs you remember setting up.
  • Confirm the exact build. Oracle's fixed releases include Java 17.0.21.1, 21.0.13.1 and 8u513, and OpenJDK 17.0.6 and later are affected.
  • Patch internet-facing services first, then restart the affected processes so the fix actually loads into memory.
  • If you cannot patch yet, restrict external access with firewall rules and limit who can reach admin interfaces.
Not sure what is running Java across your network?: Our team can inventory your systems, patch the flaw, and lock down anything that cannot wait.

Frequently Asked Questions

Is Java4Shell being exploited in the wild?

Not as of this advisory. Researchers say there is no universal exploit and attacks may need extra steps depending on the app, but CISA still recommends patching immediately because the fix is already available.

We do not install Java, so are we affected?

Possibly. Java is often bundled inside other business software such as Jira, Confluence, Jenkins and Keycloak, so you can be exposed without ever installing Java yourself. A proper inventory is the only way to be sure.

Which Java versions do we need?

Oracle released fixed builds on 17 November 2026, including Java 17.0.21.1, 21.0.13.1 and 8u513. OpenJDK 17.0.6 and later are affected, so move to the latest patched build from your distribution.

What if we cannot patch straight away?

Restrict external access to Java services with firewall rules, lock down admin interfaces, and prioritise anything internet facing. Then apply the fixed build and restart the affected processes as soon as you can.

Worried about hidden Java in your systems?

We will inventory every Java runtime across your network, patch what needs patching, and lock down what cannot wait, so you are covered before anyone builds a working exploit.


Related Guide

Cybersecurity for Sydney SMBs

Explore our complete guide to protecting your business from cyber threats.

Read the Full Guide →