· intuitem · News  · 5 min read

Java4Shell (CVE-2026-114938): CISO Assistant is not affected

A memory corruption flaw in the Java Base64 decoder can lead to remote code execution in Jira, Jenkins, Keycloak and other Java applications. CISO Assistant does not use Java, so it is not affected. Here is what the flaw is, and what to do if you run Java elsewhere.

A memory corruption flaw in the Java Base64 decoder can lead to remote code execution in Jira, Jenkins, Keycloak and other Java applications. CISO Assistant does not use Java, so it is not affected. Here is what the flaw is, and what to do if you run Java elsewhere.

Several customers have asked us about Java4Shell (CVE-2026-114938), the Java vulnerability disclosed on November 17, 2026. The short answer: CISO Assistant is not affected, because it contains no Java. This post explains the vulnerability briefly, why we are not exposed, and what we recommend if you run Java elsewhere in your environment.

What Java4Shell is

Java4Shell is a flaw in the Java runtime itself, not in a library or a framework. Java has a fast, processor-specific version of its Base64 decoder (java.util.Base64). On some inputs, this version gets the length of the output wrong and writes 62 or 63 bytes past the end of its buffer. An attacker who can make an application decode a short, malformed Base64 string can corrupt memory, and in some cases run code.

Oracle rates it 8.1 (CVSS v3.1). Calif, the researchers who found it, rate it 9.2 (CVSS v4.0). Three conditions must all be met:

  • A Java 17 or later runtime. Java 17, 21, 25 and 27 are affected, as are the end-of-life versions in between. Standard Java 8 and 11 are not.
  • An x86-64 processor with AVX-512 VBMI: Intel Xeon from Ice Lake onwards, or AMD Zen 4 and newer. ARM servers, including AWS Graviton and Apple Silicon, are not affected.
  • Attacker-controlled Base64 reaching the decoder. This is very common: authentication headers, tokens, SAML messages and file uploads are all Base64-encoded.

Calif reports code execution before login in Keycloak, Atlassian Jira and Confluence, JFrog Artifactory, Jenkins and PingFederate, and after login in Kafka, Solr, Elasticsearch, Gerrit and Spinnaker. The list is not exhaustive. As of November 18, other research teams have reproduced crashes and memory leaks but not yet code execution, and we are not aware of exploitation in the wild. The CVE is not in CISA’s Known Exploited Vulnerabilities catalog.

Why CISO Assistant is not affected

CISO Assistant does not contain or run Java, in any edition or deployment mode:

  • The backend is Python (Django), built on a Python base image.
  • The frontend is SvelteKit, running on Node.js.
  • The other services in the standard deployment are Caddy (reverse proxy, written in Go), PostgreSQL, and optionally Qdrant (written in Rust) for the AI features and our MCP server (Python).

The public repository contains no Java source files, no JAR files and no Maven or Gradle build. We also inspected the latest published container images for Community and Pro (backend, frontend and MCP server): none of them contains a Java runtime. Our SaaS runs the same images. Our website, intuitem.com, is built with Astro and served by Cloudflare, also without Java.

No action is needed on your CISO Assistant instances.

One point to check: if you connect CISO Assistant to Keycloak for single sign-on, Keycloak runs on Java and is on Calif’s list of products exploitable before login. Patch it as described below. The same applies to Jira if you use it alongside CISO Assistant.

If you run Java elsewhere

Java runs a large share of enterprise software: identity providers, ticketing, CI/CD, search and messaging, and many internal applications. Prioritise anything reachable from the internet.

1. Find your exposed Java runtimes

Inventory every Java runtime, including those bundled inside applications, appliances and container images, which often ship their own copy. For each one, note the version and the processor it runs on. On Linux, a host is in scope only if grep -o -w 'avx512vbmi' /proc/cpuinfo | head -1 returns a result. Cloud instances count too: recent Intel and AMD instance types support AVX-512 VBMI.

2. Patch

Patching is the only complete fix. Oracle’s fixed Java SE builds, published on November 17, are:

BranchFixed in
2727.0.1.1
2525.0.5.1
2121.0.13.1
1717.0.21.1

Other OpenJDK distributions (Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft, Red Hat, Linux distribution packages) release on their own schedule. Amazon has already fixed Corretto, while several Linux distributions were still preparing packages on November 18. Check your vendor’s advisory rather than comparing version numbers. End-of-life lines (18 to 20, 22 to 24, 26) will not be fixed: move to a supported version. For applications that bundle their own runtime, such as Jira or Keycloak appliances, follow the vendor’s advisory. Restart the application after updating.

3. Mitigate until you can patch

Calif suggests two JVM options. They are not in the Oracle or OpenJDK advisories, and neither replaces the patch:

  • -XX:-UseBASE64Intrinsics turns off the fast Base64 decoder and uses the regular one. This is the narrower option. Applications that decode a lot of Base64 may run slightly slower.
  • -XX:UseAVX=2 stops Java from using AVX-512 instructions at all. Use it only on x86-64: a Java runtime on ARM will refuse to start with this option.

Add the option where the application sets its JVM options (often JAVA_OPTS or JAVA_TOOL_OPTIONS) and restart. Until patched, also take internet-facing Java applications off the public network where you can, or put them behind a VPN or an access proxy.

4. Look for signs of compromise

  • Unexpected JVM crashes, especially hs_err_pid*.log files that mention Base64 decoding.
  • A Java process starting a shell or an unusual child process. This is the strongest sign.
  • Requests with short, malformed Base64 values in headers, cookies or parameters, followed by errors or restarts.

References

If you have questions about your CISO Assistant deployment, contact us.

Back to Blog

Related Posts

View All Posts »
What's New in CISO Assistant — Week 48, 2026 (v4.2.3 – v4.3.0)

What's New in CISO Assistant — Week 48, 2026 (v4.2.3 – v4.3.0)

v4.3.0 lets AI apps connect to the MCP server with an OAuth sign-in, adds an evidence review queue with a four-eyes option, a briefing-style home page, a richer framework report with evidence zips, scenario selection across risk assessments and their exports, a denser control plan, federated service accounts, a dedicated space for third parties and optional memcached, plus ITSP.10.033, ISO 14001:2015, LYSS and a Hungarian NIS2 preset.