Contact us
← Article questionsDoes this affect us?

CVEHit Business Advisory by IntegrityLab.ai

Does this affect us?

Java4Shell: Java flaw can let attackers take over some servers — CVE-2026-114938: Business Triage

Check these three things.

  1. System owner: find every Java runtime, including Java inside other products, and confirm whether it needs the November 17 update (Java 17.0.21.1, 21.0.13.1, 25.0.5.1 or 27.0.1.1).
    Affected versions and fixes
    • Oracle Java SE 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3 are affected, and earlier releases in those lines (Oracle, OpenJDK advisory).
    • Sources differ on the oldest affected build. Oracle and OpenJDK use general wording ("and earlier"). The reporting researchers (Calif) say OpenJDK is affected from 17.0.6 or newer. This page does not resolve the difference.
    • Oracle Java SE 8 Performance Pack 8u511b33-perf is also listed as affected.
    • Oracle GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3, and Oracle GraalVM Enterprise Edition 21.3.20.0.3, are affected.
    • OpenJDK marks Java 17, 21, 25 and 27 as affected, not Java 8 or 11.
    • Fixed: Java 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1, released November 17, 2026. Oracle's security baseline is now 17.0.21.1+4, 21.0.13.1+4, 25.0.5.1+4 and 27.0.1.1+4.
    • Java builds from other vendors (for example Amazon, Microsoft, Red Hat, Azul, Eclipse) are built from OpenJDK and ship their own updates. Check each vendor's notice for its version number.
    • Java is often bundled inside other products, container images and appliances, and may not appear as a separate entry in software inventories (CISA). Siemens lists some Industrial Edge Management products as affected.
    • Record for each system:
      • Java vendor and version.
      • Source of that record.
      • Date checked.
  2. Operations owner: check which affected Java systems run on x86-64 servers with AVX-512 VBMI processors.
    When the risk applies
    • The flaw is in the x86-64 version of Java's built-in Base64 decoder (CISA). The reporting researchers say it needs an x86-64 processor with AVX-512 VBMI, such as Intel Xeon Ice Lake or newer, or AMD Zen 4 or newer. They say ARM64 servers are not affected.
    • The attacker needs no account, only a way to send data that the application decodes as Base64 (Oracle: "supplying data to APIs ... such as through a web service"). Base64 is common in sign-in, file uploads and messages.
    • Calif says a client-side path also exists: a Java program that opens a TLS connection to a malicious server can be compromised even if it runs no service of its own. Internet exposure is not the only route.
    • Calif says it showed pre-authentication code execution in the default setup of Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate. Calif says the list is not complete.
    • The CVSS vector includes AV:N, meaning network-reachable, including internal networks. It is not proof of Internet exposure.
    • Cloud servers can change processor type when resized or moved. Record the processor at the time checked.
  3. Security owner: check records for unexpected Java crashes or unexpected Java processes on affected systems.
    What the records can show
    • CISA advises monitoring for rogue runtimes, unexpected Java crashes and suspicious Java processes.
    • Limits:
      • Java can crash for unrelated reasons.
      • Clean records do not prove no attack happened.
      • Missing records leave the question open.

If records show a break-in, start incident response now. Install the November 17 Java update whether or not the processor appears affected.

← Back to article questions

How can we help?

Initial enquiries only. Omit passwords, access tokens, security reports or other sensitive information. We’ll arrange secure sharing if needed.

Privacy & data handling ↗. Submitting this form does not authorise an assessment.

Checking enquiry availability…