CVE-2026-47057
OpenJDK JDK vulnerability analysis and mitigation

Overview

CVE-2026-47057 is a Denial of Service vulnerability in the Scripting component of Oracle Java SE, disclosed as part of Oracle's Critical Patch Update for July 2026. Affected versions include Oracle Java SE 8u491, 8u491-perf, and 11.0.31. The vulnerability is easily exploitable by unauthenticated remote attackers and carries a CVSS v3.1 base score of 7.5 (High) (Oracle CPU Jul 2026). The vulnerability was reported to Oracle by researchers 4ra1n, pyn3rd, and unam4 (Oracle CPU Jul 2026).

Technical details

The vulnerability resides in the Scripting component of Oracle Java SE and is classified as a Denial of Service issue (CWE category: availability impact only). An unauthenticated attacker with network access via multiple protocols can exploit this vulnerability to cause a hang or frequently repeatable crash of the affected Java SE instance. Exploitation can occur through APIs in the Scripting component — for example, via a web service that supplies data to those APIs — and also applies to Java deployments running sandboxed Java Web Start applications or sandboxed Java applets that load untrusted code from the internet (Oracle CPU Jul 2026). No authentication or user interaction is required, and attack complexity is low.

Impact

Successful exploitation results in a complete Denial of Service — specifically, the ability to cause a hang or frequently repeatable crash of Oracle Java SE. There is no reported impact on confidentiality or integrity; the vulnerability is limited to availability. Affected deployments include both server-side Java applications exposed via web services and client-side sandboxed Java environments (Java Web Start, Java applets) that process untrusted code (Oracle CPU Jul 2026).

Exploitation steps

  1. Reconnaissance: Identify internet-facing services running Oracle Java SE versions 8u491, 8u491-perf, or 11.0.31, particularly those exposing web services or APIs that utilize the Java Scripting component (e.g., via JSR 223 script engines such as Nashorn).
  2. Identify target endpoint: Locate a web service or API endpoint that passes attacker-controlled data to the Java Scripting APIs (e.g., a REST or SOAP endpoint that evaluates scripts server-side).
  3. Craft malicious payload: Construct a specially crafted input (script or data) designed to trigger a hang or crash in the Scripting component when processed by the vulnerable Java SE runtime.
  4. Send request: Transmit the crafted payload to the target endpoint over any supported network protocol (HTTP, HTTPS, etc.) without requiring credentials.
  5. Achieve DoS: The vulnerable Scripting component processes the malicious input, causing the Java SE process to hang or crash repeatedly, resulting in service unavailability (Oracle CPU Jul 2026).

Indicators of compromise

  • Network: Repeated or anomalous requests to web service endpoints that invoke Java Scripting APIs, particularly with unusual or oversized script payloads; unexpected spikes in traffic to Java application servers.
  • Logs: Java application logs showing repeated ScriptException errors, JVM crash logs (hs_err_pid*.log) generated by the Java process, or thread dump entries indicating hung threads in the Scripting component.
  • Process: Java process (java) consuming 100% CPU or becoming unresponsive; repeated JVM restarts or watchdog-triggered restarts of the application server.
  • File System: Presence of JVM crash dump files (hs_err_pid*.log) in the Java working directory following service disruptions.

Mitigation and workarounds

Oracle strongly recommends applying the July 2026 Critical Patch Update patches as soon as possible. Affected versions (Oracle Java SE 8u491, 8u491-perf, and 11.0.31) should be upgraded to the patched releases provided in the CPU. As a temporary workaround, network access to services exposing the vulnerable Scripting APIs can be restricted via firewall rules or network segmentation to reduce exposure. Oracle notes that blocking required network protocols may break application functionality and should not be considered a long-term solution (Oracle CPU Jul 2026).

Community reactions

The vulnerability was disclosed as part of Oracle's large July 2026 Critical Patch Update, which addressed 1,449 new security patches across Oracle's product portfolio. Security vendors Qualys and Tenable have already added detection coverage for CVE-2026-47057. No notable independent researcher commentary or significant social media discussion specific to this CVE has been identified at this time.

Additional resources


SourceThis report was generated using AI

Related OpenJDK JDK vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-47063HIGH7.5
  • OpenJDK JDK logoOpenJDK JDK
  • java-21-openjdk-static-libs-slowdebug
NoYesJul 21, 2026
CVE-2026-47057HIGH7.5
  • OpenJDK JDK logoOpenJDK JDK
  • openjdk-11
NoYesJul 21, 2026
CVE-2026-47058HIGH7.4
  • OpenJDK JDK logoOpenJDK JDK
  • java-1.8.0-openjdk-devel-slowdebug
NoYesJul 21, 2026
CVE-2026-60147MEDIUM6.5
  • OpenJDK JDK logoOpenJDK JDK
  • java-21-openjdk-devel
NoYesJul 21, 2026
CVE-2026-47059LOW3.7
  • OpenJDK JDK logoOpenJDK JDK
  • java-1.8.0-openjdk-demo-slowdebug
NoYesJul 21, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management