CVE-2026-47063 in Java SE
Summary
by MITRE • 07/22/2026
Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Libraries). Supported versions that are affected are Oracle Java SE: 8u491, 8u491-perf, 11.0.31, 17.0.19, 21.0.11, 25.0.3, 26.0.1; Oracle GraalVM for JDK: 17.0.19 and 21.0.11; Oracle GraalVM Enterprise Edition: 21.3.18. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. CVSS 3.1 Base Score 7.5 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N).
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 07/22/2026
This vulnerability resides within the libraries component of Oracle Java SE and related GraalVM products, representing a significant security weakness that affects multiple version streams including Java SE 8u491, 8u491-perf, 11.0.31, 17.0.19, 21.0.11, 25.0.3, 26.0.1, as well as specific GraalVM versions 17.0.19 and 21.0.11 in both standard and enterprise editions. The flaw demonstrates characteristics of an easily exploitable vulnerability requiring no authentication or user interaction, making it particularly dangerous for network-based attacks. The CVSS 3.1 score of 7.5 with a vector of AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N indicates this vulnerability specifically targets integrity impacts while maintaining low attack complexity and no privilege requirements.
The technical nature of this flaw allows an unauthenticated attacker to compromise critical data through multiple network protocols, potentially enabling unauthorized creation, deletion, or modification access to all accessible data within the affected systems. This vulnerability can be exploited using APIs within the specified component, making web services that supply data to these APIs particularly vulnerable attack vectors. The exploitation pathway extends beyond traditional server deployments to include client-side Java applications such as sandboxed Java Web Start applications and applets that load untrusted code from internet sources and rely on Java sandbox security mechanisms.
From an operational perspective, this vulnerability poses substantial risk to organizations deploying affected Java SE or GraalVM versions in production environments. The impact extends to both server-side deployments where Java applications process sensitive data and client-side scenarios where users execute potentially malicious code through web-based interfaces. The vulnerability's applicability to sandboxed environments means that even systems designed with security isolation mechanisms may be compromised if they rely on flawed library implementations. Organizations running Java applications in cloud environments, enterprise applications, or any system processing untrusted input through Java APIs face significant exposure risks.
Security mitigations should prioritize immediate patching of affected versions to address the root cause within the libraries component. Organizations should implement network segmentation and access controls to limit potential attack vectors, particularly focusing on preventing unauthorized network access to systems running vulnerable Java implementations. Additional defensive measures include disabling unnecessary Java applet and Web Start functionality, implementing strict input validation for APIs that interface with vulnerable components, and monitoring system logs for suspicious activities related to data modification attempts. According to CWE classification, this vulnerability aligns with CWE-284 Access Control Issues, while the attack patterns correspond to ATT&CK techniques involving privilege escalation through software exploitation and data manipulation. Regular security assessments should verify that patched systems maintain proper integrity controls and that no unauthorized modifications have occurred during the vulnerability window.
The vulnerability's susceptibility across multiple Java SE and GraalVM versions indicates a systemic issue within the library implementation that requires comprehensive remediation efforts rather than isolated fixes for individual components. Organizations must conduct thorough inventory assessments to identify all affected deployments, including legacy systems that may continue using older Java versions despite known vulnerabilities. Security teams should also implement monitoring protocols specifically designed to detect potential exploitation attempts targeting this integrity flaw, particularly in environments where Java applications process sensitive data or serve as integration points for external services.