Skip to main content
VulnerabilityPublished Updated

CVE-2025-50059: Oracle Java SE · Improper Access Control

Affects Oracle Java SESource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.6 High.

Data as of 9 Nov 2026, 23:24 UTC

CVSS 3.1 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Mavencom.oracle.java/java-sepkg:maven/com.oracle.java/java-seOther threatsAffected
  • 11.0.27 – 24.0.1
4 affected builds
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Monitor Oracle security advisories closely and apply official patches immediately once released for all affected Java SE and GraalVM versions.
  2. In the interim, restrict or disable the use of Java Web Start applications and sandboxed Java applets that load untrusted code, especially from unverified sources.
  3. Implement network-level controls to limit exposure of vulnerable Java clients to untrusted networks or restrict protocols that could be used for exploitation.
  4. Employ application whitelisting and code signing policies to ensure only trusted Java code is executed in client environments.
  5. Conduct thorough inventory and version management of Java runtimes across the organization to identify and remediate vulnerable instances.
  6. Enhance monitoring and logging for unusual Java application behaviors that may indicate exploitation attempts.
  7. Educate users about the risks of running untrusted Java applications and enforce policies to prevent their execution.
  8. Consider deploying endpoint detection and response (EDR) solutions capable of detecting exploitation attempts targeting Java sandbox bypasses.
  9. For critical environments, consider isolating Java client applications or running them in hardened virtualized or containerized environments to limit impact.
  10. Review and update incident response plans to include scenarios involving Java sandbox bypass vulnerabilities.

Description

The OpenJDK runtime environment. Security Fix(es): Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Networking). Supported versions that are affected are Oracle Java SE: 8u451-perf, 11.0.27, 17.0.15, 21.0.7, 24.0.1; Oracle GraalVM for JDK: 17.0.15, 21.0.7 and 24.0.1; Oracle GraalVM Enterprise Edition: 21.3.14. 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. While the vulnerability is in Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability 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. This vulnerability does not apply to Java deployments, typically in servers, that load and run only trusted code (e.g., code installed by an administrator). CVSS 3.1 Base Score 8.6 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N).(CVE-2025-50059)

References

Community reviews

Loading reviews…