Support Bulletin. Java4Shell (CVE-2026-114938), What You Need to Know

  • Updated

Originally published November 18, 2026

On November 17, 2026 the research firm Calif disclosed Java4Shell, a memory corruption vulnerability in the Base64 decoder of OpenJDK 17 and later, rated 9.2 under CVSS 4.0. The flaw lives in the Java runtime itself rather than in any library, so dependency scanners will not flag it. It affects Java 17, 21, 25 and 27 running on x86-64 hardware with AVX-512 VBMI support. Java 8 and 11 are not affected. As of this bulletin no exploitation in the wild has been reported.

 

What to do now

  1. Update the Java runtime, starting with internet-facing systems. Oracle JDK users should move to 17.0.21.1, 21.0.13.1, 25.0.5.1 or 27.0.1.1. If you run Temurin, Corretto, Zulu, Microsoft Build of OpenJDK, Red Hat or a Linux distribution package, wait for a build whose release notes name CVE-2026-114938 and expect it to carry a different version number from Oracle’s. Updating your application does not update the runtime beneath it, and JDKs bundled inside container images or application distributions will not appear in package manager queries. Restart the process after updating and confirm the running version.
  2. Inventory every JVM by vendor and exact build string, not just major version. Prioritize anything reachable from the internet that decodes Base64 from a request, which includes JWT validation, HTTP Basic Auth, SAML assertions and file uploads.
  3. Check your hardware. Hosts without AVX-512 VBMI do not execute the vulnerable path. ARM instances and Intel CPUs older than Ice Lake are outside the scope of this vulnerability.
  4. Hunt for failed attempts. An unsuccessful exploit usually crashes the JVM, so look for hs_err_pid files, SIGSEGV entries and unexplained restarts since November 16, along with 65-character or 129-character Base64 strings in Authorization headers, cookies and upload bodies. Treat any hit as a compromised host.

Calif’s disclosure can be found at calif.io/java4shell. Oracle’s November update notice can be found at oracle.com/security-alerts/cspunov2026.html.

 

Contrast product capabilities

Our Security Research team is evaluating how the Contrast platform and agents behave against this vulnerability, including detection of exploitation attempts and visibility into post-exploitation activity. Because the flaw sits in the runtime rather than in application code or a library, that evaluation takes care, and we will not make a claim until it is complete. This bulletin will be updated with the results.

 

Contrast’s own security posture

Contrast has identified the systems in our environment that run affected Java versions and has prioritized remediation of those systems. Patching is underway as vendor builds become available, and we are monitoring for indicators of attempted exploitation. We have seen no indication of exploitation against our platform. Customers running Contrast on-premises will receive an update with a patched runtime once one is available, and we will communicate the timing through this bulletin.

If you have any further questions please direct them to your account manager, or support@contrastsecurity.com.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request