Contact us
← CVEHit Business AdvisoryJava4Shell: Java flaw can let attackers take over some servers — CVE-2026-114938: Business Triage

CVEHit Business Advisory by IntegrityLab.ai

Published

Java4Shell: Java flaw can let attackers take over some servers — CVE-2026-114938: Business Triage8.1/10High · CVSS 3.1Oracle (CVE record)Fix availableJava update, Nov 17CISA assessmentCVE.org sourceNo KEVChecked Nov 18

Install the November 17 Java update and restart Java applications on x86-64 systems. Research: primary sources retrieved November 18, 2026.

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.

Do Now

  • System owner: install the November 17 Java update (17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1 or your vendor's matching release) and restart Java applications, starting with Internet-facing services and Java programs that connect out to outside servers.
    Proof the update is done
    • Start with Internet-facing services, including the products Calif names (Keycloak, Jira, Confluence, Artifactory, Jenkins, PingFederate).
    • The Java version reported by the running application after restart, not just the installed package. Source and date.
    • For bundled Java, the product vendor's notice naming CVE-2026-114938.
  • Operations owner: where an immediate update is not possible, apply a temporary control and record it.
    What to know
    • CISA: restrict and validate Base64 input at the application boundary, enforce input-size limits, and limit unauthenticated access.
    • The reporting researchers say starting Java with -XX:-UseBASE64Intrinsics turns off the affected decoder, or -XX:UseAVX=2 turns off AVX-512. Use -XX:UseAVX=2 only on x86-64; Java on ARM will not start with it.
    • These are stopgaps, not the fix, and are not listed by Oracle.
  • Provider: ask each vendor whose product, appliance or hosted service includes Java whether it is affected and when a fix ships.
    What to ask
    • Ask for:
      • Java vendor and version inside the product.
      • Processor type where it runs.
      • The fix date.
    • Keep the reply as evidence.

Do Next

  • Security owner: recheck CISA and Oracle for changes to the exploitation status.
    What to recheck
    • CISA's assessment in the CVE record, dated November 17, 2026.
    • The CISA KEV catalog. CVE-2026-114938 was not in catalog 2026.11.18.
    • The reporting researchers say they are holding back product-specific exploit details for now and will publish them later. Recheck when that happens.
    • Date of each recheck.

Check your own records.

  • Use your approved AI tool.
  • Require evidence. Flag unknowns.

Read the prompt

The reported finding

Base64 decoder memory corruption in the Java virtual machine

Original advisory →
Required conditions
An affected Java runtime on an x86-64 processor; the reporting researchers say AVX-512 VBMI support is required and ARM64 is not affected. Data supplied by an outside party reaches Java's Base64 decoder. Separately, Calif says a Java program that opens a TLS connection to a malicious server can be compromised.
Reported outcome
Oracle: a difficult-to-exploit flaw that lets an unauthenticated attacker with network access compromise Java SE and GraalVM, with possible takeover. Component: Compiler (OpenJDK: hotspot/compiler). CISA: crafted Base64 input could crash the JVM and allow unauthenticated remote code execution. Weakness: CWE-122, heap-based buffer overflow (CISA ADP). Oracle CVSS 3.1 8.1 High. The reporting researchers separately score it CVSS 4.0 9.2 Critical; that score is not in the CVE record.

Fix guidance

  • Oracle Critical Security Patch Update, November 2026, released November 17, 2026.
  • Fixed Java releases: 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1 (Oracle full builds +4; Oracle release notes for all four are dated November 17, 2026).
  • Other Java vendors ship matching updates under their own version numbers. Confirm with each vendor's notice.
  • These sources do not confirm the fixed release for GraalVM or the Java 8 Performance Pack. Check Oracle's patch availability document.
  • Restart Java applications after updating. Confirm the running version.
  • Exploitation status: CISA SSVC in the CVE record, dated November 17, 2026: Exploitation none, Automatable no, Technical Impact total. Not in CISA KEV catalog 2026.11.18. The reporting researchers published a safe trigger test and say they are holding back product-specific exploits for now. No KEV entry and Exploitation none do not prove no attacks occurred.
  • NVD status: Undergoing Analysis, checked November 18, 2026.

What IntegrityLab.ai can check

  • This advisory does not mean IntegrityLab.ai detects CVE-2026-114938.
  • When enabled for an authorized assessment, IntegrityLab.ai's discovery records reachable web services and the server details they return. This gives your administrator a starting point. It does not currently offer a validated check for this CVE, identification of the Java version or processor behind a service, confirmation of a package's fixes, or proof of compromise.
  • A service that looks like Java is a clue, not proof of the runtime version, processor or fix status.

How to read the score

Oracle (CVE record) CVSS 3.1: 8.1 (High). CVSS 4.0: 9.2 (Calif, researcher): Critical. Use the conditions and update history alongside the score to set your priorities.

Sources and vendor guidance

Need an independent review of your public exposure?

See IntegrityLab.ai →

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…