← All security news

Java4Shell Flaw Hits Jenkins, Jira, Struts

A cracked OpenJDK coffee-cup icon labelled with a critical remote-code-execution flaw, with lines fanning out to three smaller boxes labelled CI/CD, Ticketing, and Identity, representing a single JVM vulnerability that reaches into many kinds of business software built on Java

Security researchers disclosed a critical flaw in OpenJDK on 17 November, nicknamed "Java4Shell" and tracked as CVE-2026-114938. The bug sits in the hardware-accelerated Base64 decoder built into the JVM: a specially crafted piece of Base64 data can corrupt memory and, on affected systems, let an attacker run their own code with no login required. It carries a CVSS score of 9.2 under the newer CVSS 4.0 scale (Oracle rates it 8.1 under the older CVSS 3.1 system) — either way, it's a critical-severity flaw in software that sits underneath an enormous amount of business infrastructure.

The flaw affects OpenJDK 17.0.6 and later across essentially every major distribution: Oracle Java SE, Amazon Corretto, Eclipse Temurin, Microsoft's Build of OpenJDK, Azul Zulu, and Red Hat's OpenJDK. Because so much enterprise software runs on Java underneath the hood, the practical reach goes well beyond "Java developers": Jenkins build servers, Atlassian Jira and Confluence, Keycloak and PingFederate identity services, JFrog Artifactory, and applications built on Apache Struts or Spring Boot are all named as potentially exposed. Oracle shipped a fix on 17 November as part of its regular security update, patching eleven Java-related flaws in total. CISA followed with an alert the same day urging organisations to patch immediately, prioritising anything internet-facing. As of this writing, there are no confirmed reports of the flaw being exploited in the wild — researchers have demonstrated the underlying memory corruption, but a ready-to-use attack tool has not been published.

What this means for your business

Most business owners don't think of their software as "running on Java" — but a striking number of the tools behind the scenes do. If your developer or IT provider uses Jenkins to build and deploy your website or app, Jira or Confluence to manage projects, or Keycloak to handle logins, this flaw is relevant to you even though you've never typed a line of Java yourself.

Three things worth doing this week. First, ask whoever manages your infrastructure — your development agency, your IT provider, or an in-house team — whether any system they run is built on Java 17 or later, and whether CVE-2026-114938 has been patched on it. Second, flag anything internet-facing specifically: a build server or admin panel exposed to the public internet is a much higher priority than one that's only reachable from inside your office network. Third, if a full patch can't go out immediately, ask whether the stopgap Oracle published — disabling the hardware-accelerated Base64 path on the JVM — has been applied in the meantime. None of this requires you to understand Java; it just requires asking the right question of the people who run your systems, this week rather than next month.

Questions about your own setup? contact@techleetsolutions.com
Sources: BleepingComputer, CISA, The Hacker News