Newsroom

Check out the latest news of Sparrow

Six vulnerabilities have been disclosed in Oracle Java products used to develop and run enterprise applications and web services.

On November 18, the Korea Internet & Security Agency (KISA) recommended security updates for affected releases of Oracle Java SE, JavaFX, and GraalVM.

Java4Shell is a memory-handling flaw in the OpenJDK Base64 decoder.

The decoder can write beyond its output buffer, corrupting JVM memory and interrupting service.

Depending on the runtime and how the service processes input, exploitation may expose information in process memory or lead to remote code execution.

 

■ Vulnerability overview

-Detailed Description of Each Vulnerability

CVE ID Component Potential impact Severity
CVE-2026-114938 (Java4Shell) Compiler (Base64 decoder) Information disclosure, service interruption, remote code execution Critical, CVSS v4.0 9.2. Oracle rates it High, CVSS v3.1 8.1.
CVE-2026-86144 libxml2 (Java SE and JavaFX XML processing) XML external entity injection, server-side request forgery High (CVSS v3.1 7.5)
CVE-2026-114939 JGSS (authentication and secure communication) Information disclosure, data tampering High (CVSS v3.1 7.4)
CVE-2026-114940 JSSE Information disclosure, data tampering High (CVSS v3.1 7.4)
CVE-2026-114941 Compiler Denial of service, data tampering High (CVSS v3.1 7.0)
CVE-2026-114942 Libraries Denial of service, data tampering High (CVSS v3.1 7.0)

– Affected and fixed versions

Vulnerability Product Affected build Fixed release
CVE-2026-86144 Oracle Java SE 8u511b33 8u513 (1.8.0_513-b04)
CVE-2026-86144 Oracle JavaFX 21.0.13 21.0.13.1
CVE-2026-86144 Oracle JavaFX 25.0.5 25.0.5.1
CVE-2026-86144 Oracle JavaFX 27.0.1 27.0.1.1
CVE-2026-114938 Oracle Java SE 8u511b33-perf 8u513-perf (1.8.0_513-perf-b4)
CVE-2026-114938 Oracle Java SE 17.0.21.0.3 17.0.21.1
CVE-2026-114938 Oracle Java SE 21.0.13.0.3 21.0.13.1
CVE-2026-114938 Oracle Java SE 25.0.5.0.3 25.0.5.1
CVE-2026-114938 Oracle Java SE 27.0.1.0.3 27.0.1.1
CVE-2026-114938 Oracle GraalVM for JDK 17.0.21.0.3 17.0.21.1
CVE-2026-114938 Oracle GraalVM for JDK 21.0.13.0.3 21.0.13.1
CVE-2026-114938 Oracle GraalVM Enterprise Edition 21.3.20.0.3 21.3.20.1
CVE-2026-114939 Oracle Java SE 8u511b33 8u513 (1.8.0_513-b04)
CVE-2026-114939 Oracle Java SE 8u511b33-perf 8u513-perf (1.8.0_513-perf-b4)
CVE-2026-114939 Oracle Java SE 11.0.33.0.3 11.0.33.1
CVE-2026-114939 Oracle Java SE 17.0.21.0.3 17.0.21.1
CVE-2026-114939 Oracle Java SE 21.0.13.0.3 21.0.13.1
CVE-2026-114939 Oracle Java SE 25.0.5.0.3 25.0.5.1
CVE-2026-114939 Oracle Java SE 27.0.1.0.3 27.0.1.1
CVE-2026-114939 Oracle GraalVM for JDK 17.0.21.0.3 17.0.21.1
CVE-2026-114939 Oracle GraalVM for JDK 21.0.13.0.3 21.0.13.1
CVE-2026-114939 Oracle GraalVM Enterprise Edition 21.3.20.0.3 21.3.20.1
CVE-2026-114940 Oracle Java SE 8u511b33 8u513 (1.8.0_513-b04)
CVE-2026-114940 Oracle Java SE 8u511b33-perf 8u513-perf (1.8.0_513-perf-b4)
CVE-2026-114940 Oracle Java SE 11.0.33.0.3 11.0.33.1
CVE-2026-114940 Oracle Java SE 17.0.21.0.3 17.0.21.1
CVE-2026-114940 Oracle Java SE 21.0.13.0.3 21.0.13.1
CVE-2026-114940 Oracle Java SE 25.0.5.0.3 25.0.5.1
CVE-2026-114940 Oracle Java SE 27.0.1.0.3 27.0.1.1
CVE-2026-114940 Oracle GraalVM for JDK 17.0.21.0.3 17.0.21.1
CVE-2026-114940 Oracle GraalVM for JDK 21.0.13.0.3 21.0.13.1
CVE-2026-114940 Oracle GraalVM Enterprise Edition 21.3.20.0.3 21.3.20.1
CVE-2026-114941 Oracle Java SE 21.0.13.0.3 21.0.13.1
CVE-2026-114941 Oracle Java SE 25.0.5.0.3 25.0.5.1
CVE-2026-114941 Oracle Java SE 27.0.1.0.3 27.0.1.1
CVE-2026-114941 Oracle GraalVM for JDK 21.0.13.0.3 21.0.13.1
CVE-2026-114942 Oracle Java SE 21.0.13.0.3 21.0.13.1
CVE-2026-114942 Oracle Java SE 25.0.5.0.3 25.0.5.1
CVE-2026-114942 Oracle Java SE 27.0.1.0.3 27.0.1.1
CVE-2026-114942 Oracle GraalVM for JDK 21.0.13.0.3 21.0.13.1

※ For Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft Build of OpenJDK, Red Hat OpenJDK, and other OpenJDK distributions, consult the vendor’s advisory for the applicable fixed build.

※ Previous versions of affected software may also be vulnerable. We recommend updating to a version in which the vulnerability has been resolved.

 

■ Exposure conditions

 

– CVE-2026-114938: This vulnerability may corrupt JVM memory, potentially resulting in service disruption, disclosure of information stored in process memory, or remote code execution. Actual exposure depends on whether the affected Java build is in use, whether the vulnerable Base64 acceleration path is executed in an x86-64 environment supporting AVX-512 VBMI, and whether external input is passed to that path. Services that process such input before authentication may be exploitable without requiring a login.

– CVE-2026-86144: This vulnerability may lead to unintended access to external resources or network requests. CVE-2026-114939 may result in information disclosure or data tampering. Oracle identifies environments that execute untrusted code and rely on the Java sandbox as the affected deployment scenarios for both vulnerabilities.

– CVE-2026-114940: This vulnerability may result in the disclosure of TLS-related information or data tampering. Oracle describes environments in which external data is supplied to the component’s API, as well as Java sandbox environments that execute untrusted code, as being within the scope of impact.

– CVE-2026-114941 & CVE-2026-114942: These vulnerabilities may cause service disruption or data tampering in environments where external data is supplied to the component’s API.

 

 

■ How to Check for Vulnerabilities

 

① Identify the product and build number used by the actual service.

: Check the Java version from the current terminal on Windows or Linux.

java -version

product, run the -version command using the Java executable specified in the service startup configuration. In containerized environments, check the runtime inside the container currently running the service.)

: If jcmd is available, use the following commands to identify the JVM running the service. Replace 12345 in all jcmd commands in this guide with the actual process ID (PID) of the service’s Java process.

jcmd -l
jcmd 12345 VM.version

(If JavaFX is deployed separately, check its version in the application’s dependency list or deployment package.)

→ Compare the identified product, distribution, and full build number against the security advisories published by KISA or the relevant vendor.

 

② Check CPU capabilities and JVM Base64 acceleration settings related to Java4Shell.

: To check CPU capabilities on Linux, run the following command in the environment where the service is running.

grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'

→ If all four flags—avx512f, avx512bw, avx512vbmi, and bmi2—are displayed, the execution environment meets the CPU requirements for Java4Shell.

: Check JVM settings on Windows.

jcmd 12345 VM.flags -all | findstr /I UseBASE64Intrinsics

: Check JVM settings on Linux.

jcmd 12345 VM.flags -all | grep -w UseBASE64Intrinsics

→ If UseBASE64Intrinsics is set to false, Base64 acceleration is disabled in the JVM. If it is set to true, check the CPU capabilities and patch status together. If no output is returned, verify whether jcmd executed successfully and whether the JVM supports the specified option.

③ Identify potential Base64 decoding operations related to Java4Shell and check external input paths.

: Run the following commands in the application’s source directory.

(Windows PowerShell)

Get-ChildItem -Recurse -File -Include *.java,*.kt,*.scala,*.groovy | Select-String -Pattern 'java\.util\.Base64|Base64\s*\.\s*get(Mime|Url)?Decoder\s*\('

: Linux (with ripgrep installed)

rg -n 'java\.util\.Base64|Base64\s*\.\s*get(Mime|Url)?Decoder\s*\(' -g '*.java' -g '*.kt' -g '*.scala' -g '*.groovy' .

→ Based on the search results, determine whether authentication data, file uploads, or responses from external systems are actually passed to the identified decoders. Even if no results are found, authentication frameworks, middleware, and external integration libraries may perform Base64 decoding internally. Therefore, their processing paths should also be reviewed.

 

 

■ Remediation Measures

 

✔️ Update to a security-patched version of the product and distribution in use (Refer to the table above)

Refer to the Affected Versions and Fixed Versions table above and update the product in use to a patched version. KISA advises that versions earlier than the affected versions listed in the table may also be vulnerable. Calif reports that the vulnerable Java4Shell code was introduced starting with OpenJDK 17.0.6. For other OpenJDK distributions, including Eclipse Temurin, Amazon Corretto, and Azul Zulu, check each vendor’s security advisories for the affected versions and fixed builds for each CVE.

✔️ Restart the service after updating and verify the build number actually used by the service

In containerized environments, replace the existing image with one that includes the patched Java version, redeploy the service, and check the Java version inside the running container. If JavaFX is deployed separately, also verify that the patched version is included in the deployment package.

✔️ Apply temporary mitigation measures if the Java4Shell patch cannot be applied immediately

If the security patch cannot be applied immediately, Base64 hardware acceleration can be temporarily disabled by adding the following option to the service startup parameters in OpenJDK HotSpot environments that support this option.

 

– Startup option

-XX:-UseBASE64Intrinsics

However, compatibility and performance impacts should be evaluated before applying this option. After restarting the service, run the JVM configuration check command to verify that UseBASE64Intrinsics is set to false.

※ This mitigation applies only to CVE-2026-114938. The definitive remediation is to update to a Java runtime that includes the security fix.

 

To prevent security threats arising from the disclosure of these vulnerabilities, we strongly recommend conducting prompt inspections and applying security updates in accordance with the remediation measures described above.

 


[References]
1. KISA BohoNara – Security Advisory / Oracle Product Security Update Advisory https://www.boho.or.kr/kr/bbs/view.do?bbsId=B0000133&categoryCode=&menuNo=205020&nttId=72313&pageIndex=1&searchCnd=&searchWrd=
2. Oracle – Oracle Critical Security Patch Update Advisory - November 2026 https://www.oracle.com/security-alerts/cspunov2026.html#AppendixJAVA
3. Calif – Java4Shell: Write Once, RCE Everywhere https://calif.io/java4shell
4. Oracle – Oracle jcmd Documentation https://docs.oracle.com/en/java/javase/17/docs/specs/man/jcmd.html
5. Oracle – Oracle Java Enterprise Performance Pack Release Notes https://www.oracle.com/java/technologies/javase/8u513-perf-relnotes.html