Konfirmity
All security advisories

//security advisory

Java4Shell (CVE-2026-114938): Java Security Advisory

Java4Shell is the name used for a reported memory-corruption flaw in OpenJDK, associated with CVE-2026-114938. Early research points to accelerated Base64 decoding on certain x86 processors. Remote code execution, exact affected versions and a CVE-specific fixed build remain unconfirmed in the retrieved vendor records. Inventory running Java services, check bundled runtimes and prepare vendor-supported updates. A proposed JVM workaround is available, with important limits.

On this page
  1. What is confirmed?
  2. Affected Java versions
  3. Checks and mitigation
  4. Oracle patch status
  5. Atlassian and bundled Java
  6. Detection and evidence
  7. Java4Shell FAQ
  8. Sources

What is Java4Shell, and what is confirmed?

Java4Shell is the name used in early security research for a reported OpenJDK memory-corruption flaw associated with CVE-2026-114938. The concern is that untrusted Base64 input could reach a vulnerable native decoding routine inside the JVM, potentially before an application authenticates the sender.

IONIX reports its own testing found an out-of-bounds write in this path. It explicitly says it has not demonstrated a crash or code execution. Treat unauthenticated RCE as a reported potential impact, rather than an established result.

QuestionVerified source status
CVE recordThe retrieved CNA record is reserved and has no public technical description.
SeverityEarly reports cite CVSS 4.0 9.2. No CNA score or vector was verified.
Technical evidenceIONIX reports memory corruption in its testing; reliable RCE remains unconfirmed.
ExploitationIONIX reports no known attacks or public exploit. Absence of attacks was not independently established.
FixNo retrieved vendor record maps this CVE to a confirmed fixed build.

Reviewed 17 November 2026 using Exa-retrieved sources. The upstream record review completed at 19:02 UTC; subsequent checks covered vendor tickets. Retrieval can lag a developing disclosure. Check the CVE record and your vendor advisory before making a deployment decision.

Which Java versions may be affected?

IONIX identifies HotSpot-based Java 17.0.6 and later Java 17 updates, Java 21 and Java 25 as candidates for investigation. Its preliminary exposure model requires all three conditions below. This is researcher analysis, not a vendor-confirmed affected-version matrix.

  • A runtime containing the affected HotSpot Base64 decoding path.
  • An x86-64 CPU exposing AVX-512 VBMI support to the JVM.
  • Application behavior that passes attacker-controlled Base64 input to that path.

Under this model, ARM systems and JVMs that do not use HotSpot do not execute the implicated path. That is useful for prioritizing checks, but does not establish a complete unaffected-product list. Do not downgrade to an old Java release as a workaround.

Oracle Java SE, Temurin, Corretto, Zulu and Red Hat builds need their own release verification. A runtime embedded in an application or container can differ from the Java installed on its host. Record the vendor, exact build, architecture and executable used by each service. See IONIX's scope and limitations.

How to check and mitigate Java4Shell exposure

  1. Inventory running services and bundled runtimes

    Start with internet-facing Java services, then internal services accepting untrusted data, CI agents and packaged applications. Identify the actual JVM used by each process, not only the default java on PATH.
  2. Assess whether the reported path is reachable

    Check runtime build, CPU features, JVM flags and where the application decodes untrusted Base64. Authentication headers, tokens and request fields are triage candidates, not proof that a particular product is vulnerable.
  3. Reduce unnecessary exposure

    Restrict unnecessary public endpoints with network controls. Do not treat a WAF rule as complete protection: the input may reach the service through different fields or paths.
  4. Test a provisional workaround where needed

    IONIX reports that disabling Base64 intrinsics stopped the write in its Java 17.0.21 test. Validate startup, application behavior and performance before rollout. This is not a verified vendor-endorsed workaround.
  5. Apply the vendor-confirmed fix and restart

    When your distributor identifies a fixed build for this CVE, install it, rebuild container images and replace running instances. Restart long-lived JVMs and verify their runtime build. Updating a package does not replace a JVM already in memory.

Read-only inventory commands

Runtime and CPU inventory
java -version
java -XX:+PrintFlagsFinal -version 2>&1 | rg 'UseAVX|UseBASE64Intrinsics'
lscpu

On Linux, inspect lscpu for avx512_vbmi. These commands describe the JVM you launch and the CPU features visible in that environment, not the configuration of an existing service. Use the service's exact Java executable, and inspect its launch configuration or running-JVM diagnostics separately. A missing flag is not proof of safety.

Researcher-proposed JVM setting

JVM startup option, requires restart
-XX:-UseBASE64Intrinsics

Add this option through the application's supported JVM configuration mechanism. After restart, verify that UseBASE64Intrinsics is false in the running service. IONIX also reports success with limiting AVX to level 2, but neither measure is a replacement for a confirmed patch. Its findings do not establish protection for every distribution or attack path. Source: IONIX mitigation testing.

Oracle Java patch status and fixed versions

Oracle's November 17 pre-release notice announces 11 Java SE fixes, all described as potentially exploitable remotely without credentials. Its highest Java SE score is CVSS 3.1 8.1. The retrieved notice does not identify the individual CVEs, so neither that score nor its affected-product list can be assigned to Java4Shell. CVSS 3.1 and 4.0 scores are also different scoring systems.

Oracle release listings, not confirmed Java4Shell fixes
Java lineBuild listed by Ops.java
88u513
1111.0.33.1
1717.0.21.1
2121.0.13.1
2525.0.5.1
2727.0.1.1

Oracle has published release notes dated 17 November for JDK 17.0.21.1+4 and JDK 21.0.13.1+4. They confirm security update releases, but do not enumerate the CVEs fixed or identify a Java4Shell fix.

Ops.javalabels these builds current, while the retrieved Oracle advisory remains pre-release. Follow Oracle's supported update guidance, but confirm a release note or advisory naming CVE-2026-114938 before closing this specific finding. Oracle version numbers do not establish the fixed package versions for other distributors.

Other component CVEs to check in JDK update inventories

These component issues are separate from Java4Shell. Their descriptions are documented upstream or by vendors; inclusion in a particular November JDK build still requires that distributor's CVE mapping. The retrieved Oracle release notes do not provide it.

CVE / sourceComponent and documented issue
CVE-2026-46675libpng: stale-pointer read during png_read_end after incomplete metadata decompression. Fixed upstream in 1.6.59; exposure requires a particular reader call sequence.
CVE-2026-50811FreeType: out-of-bounds read in TT_Get_Var_Design during variable-font processing.
CVE-2026-95512FreeType: repeated subroutine allocations and decryptions in the CID font loader can exhaust CPU and memory.
CVE-2026-27171zlib: an infinite loop in x2nmodp reached through crc32_combine64 or crc32_combine_gen64. This is a CRC32 combine issue, not an inflate decoder flaw.

The FreeType 2.15.0 release discussion identifies fixes for both font CVEs and its vendored zlib copy. An upstream library release does not establish which JDK builds include it or whether the affected path is used by a Java application.

Atlassian advisories and software that bundles Java

Check self-managed applications as well as standalone Java installs. Atlassian publishes product-level fixes for vulnerable dependencies, and those updates matter. The four tickets below identify different CVEs, however. They provide no evidence that their fixed product versions remediate Java4Shell.

Separate Atlassian dependency fixes, not CVE-2026-114938 fixes
Product / ticketIssue identified by AtlassianTicket fixed versions
Bitbucket Data Center: BSERV-20635CVE-2026-8798: Bouncy Castle denial of service10.0.0, 9.4.26
Bamboo Data Center: BAM-26642CVE-2026-47884: Spring file inclusion12.1.13
Confluence Data Center: CONFSERVER-104567CVE-2026-71290: HttpClient TLS hostname verification10.2.19, 9.2.27
Confluence Data Center: CONFSERVER-104578CVE-2026-103119: Tomcat information disclosure11.0.1

These are the fixed versions for each individual ticket, not a recommendation to stop at that release. Consult the November security bulletin for the broader supported update target. Atlassian notes that a dependency's critical score can represent a lower assessed risk in its products because of how that component is used.

For Java4Shell, record the JRE actually used by Jira, Confluence, Bitbucket, Bamboo and their agents. Follow the product's supported Java configuration and compatibility guidance. A host-level JDK update can leave a bundled runtime unchanged. The reviewed Atlassian bulletin, index and these tickets do not identify CVE-2026-114938; no Atlassian-specific fix for it is verified here.

Detection, incident review and remediation evidence

IONIX recommends monitoring unexpected JVM instability, including hs_err_pid crash logs, unusual child processes and unexpected outbound connections. Malformed Base64 errors can guide investigation, but ordinary bad input can produce them too. No CVE-specific indicator was independently validated in this review. Avoid triggering memory corruption against production systems to test exposure.

  • Preserve crash reports, relevant requests, process events and timestamps if suspicious activity appears.
  • Record each service owner, runtime vendor/build, CPU features and exposure assessment.
  • Keep workaround configuration, restart evidence, application checks and any performance impact.
  • Close remediation only with a vendor-confirmed fix, the deployed build and a verified service restart.

Use the same workflow as your vulnerability management and change management processes. Keep provisional risk reduction separate from verified remediation.

Java4Shell CVE-2026-114938 FAQ

What is Java4Shell (CVE-2026-114938)?

Java4Shell is a reported OpenJDK memory-corruption vulnerability associated with CVE-2026-114938. IONIX's own testing found an out-of-bounds write in an accelerated Base64 decoding path, but did not demonstrate code execution. The retrieved CVE record was still reserved on 17 November 2026.

Which Java versions are affected by Java4Shell?

IONIX's preliminary research identifies HotSpot Java 17.0.6 and later Java 17 updates, Java 21 and Java 25, with AVX-512 VBMI support and attacker-controlled Base64 input. This is a triage scope, not a vendor-confirmed affected-version matrix. Oracle's wider November patch list does not establish this CVE's scope.

Which Java version fixes CVE-2026-114938?

No CVE-specific fixed build was verified in the sources retrieved for this review. Ops.java lists newer Oracle builds, including 17.0.21.1 and 21.0.13.1, but the retrieved Oracle pre-release notice does not map its fixes to this CVE. Verify your Java distributor's release notes before recording this issue as remediated.

Is there a temporary Java4Shell workaround?

IONIX reports that starting HotSpot with -XX:-UseBASE64Intrinsics stopped the out-of-bounds write in its Java 17.0.21 test. This is a researcher-proposed measure, not a verified Oracle-endorsed workaround. Test compatibility and performance, restart the service and verify the flag in the running JVM. Apply a vendor-confirmed fix when available.

Has Atlassian released a Java4Shell fix?

The Atlassian November 17 bulletin and advisory index retrieved for this review did not identify CVE-2026-114938. Their product fixes cannot therefore be described here as Java4Shell fixes. Check the exact CVE in Atlassian's advisory portal and identify the JRE actually used by each self-managed installation.

Is Java4Shell being exploited in the wild?

IONIX reported no known exploitation or public exploit in its 17 November update. This review did not independently establish the absence of attacks. Treat unexpected JVM crashes as investigation signals, not proof of exploitation or proof of safety.

Sources and verification limits

This advisory distinguishes vendor records from preliminary researcher findings. It does not treat a reported score, release listing or unrelated product patch as confirmation of CVE-specific exploitability or remediation.