dbcve.org
JreApplication · Oracle

CVE-2025-50059

HIGH · 8.6 CVSS v3.1 Published 2025-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A network-based vulnerability in the Java SE and GraalVM networking component allows unauthenticated remote attackers with network access to compromise affected installations. The vulnerability enables unauthorized access to critical data or complete access to all accessible data, specifically impacting sandboxed Java deployments running untrusted code (Java Web Start applications or applets that load code from the internet).

MitigationUpgrade to patched Oracle Java SE versions (8u461+, 11.0.25+, 17.0.21+, 21.0.9+, 24.0.3+) or GraalVM versions that include the security fix. For deployments that cannot upgrade immediately, ensure Java sandbox restrictions are enforced and avoid loading untrusted code from the network.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JreApplication
Affected:= 1.8.0= 11.0.27= 17.0.15= 21.0.7= 24.0.1
JdkApplication
Affected:= 1.8.0= 11.0.27= 17.0.15= 21.0.7= 24.0.1
Graalvm For JdkApplication
Affected:= 17.0.15= 21.0.7= 24.0.1
GraalvmApplication
Affected:= 21.3.14

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Java/JDK version
    Run 'java -version' (for JRE) or 'javac -version' (for JDK) from command line. For Oracle JDK installations, also check the release file in the JAVA_HOME directory: cat $JAVA_HOME/release | grep 'IMPLEMENTOR' or check $JAVA_HOME/lib/VERSION.TXT
    Affected if Version is earlier than 8u461 (for Java 8), earlier than 11.0.25 (for Java 11), earlier than 17.0.21 (for Java 17), earlier than 21.0.9 (for Java 21), or earlier than 24.0.3 (for Java 24)
  2. Identify installed GraalVM version
    Run 'graalvm --version' or check the version string in the GRAALVM_HOME directory. Look for VERSION file or execute: java -version within the GraalVM environment
    Affected if GraalVM for JDK version is earlier than 17.0.15, 21.0.7, or 24.0.1, OR standalone GraalVM version is 21.3.14 or earlier
  3. Determine if Java Web Start is enabled
    Check for javaws executable: which javaws (Linux/Mac) or where javaws (Windows). Also check if JRE has the javaws component installed in the bin directory
    Affected if javaws is installed and available on the system, as this feature loads untrusted code from the network
  4. Determine if Java applets are supported
    Check if browser plugins or older Java plugin components are configured. Look for deployment.config or deployment.properties files in the JRE lib directory that may enable applet support
    Affected if Applet support is enabled or configured in the Java deployment settings, as applets can load code from the network into the sandbox
  5. Check for network-exposed Java services
    Review any running Java processes that bind to network interfaces (ports). Use 'netstat -tulpn | grep java' or 'ss -tulpn' to list Java processes listening on network ports, particularly if running untrusted code
    Affected if Java applications with network exposure are running and may execute untrusted code loaded from the network

Environment is affected if running an unpatched Oracle Java or GraalVM version (earlier than 8u461/11.0.25/17.0.21/21.0.9/24.0.3) AND Java Web Start, applets, or other sandboxed code loading from network is enabled

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to patched Oracle Java SE versions (8u461+, 11.0.25+, 17.0.21+, 21.0.9+, 24.0.3+) or GraalVM versions that include the security fix. For deployments that cannot upgrade immediately, ensure Java sandbox restrictions are enforced and avoid loading untrusted code from the network.

Recommended fix High confidence

Oracle Java SE: 8u461+/11.0.28+/17.0.16+/21.0.8+/24.0.2+ | Oracle GraalVM for JDK: 17.0.16+/21.0.8+/24.0.2+ | Oracle GraalVM Enterprise Edition: patched version after 21.3.14

  1. Identify the current Oracle Java SE, Oracle GraalVM for JDK, or Oracle GraalVM Enterprise Edition version installed using 'java -version' or checking the product documentation
  2. For Oracle Java SE 8u451-perf: upgrade to Java 8u461 or later
  3. For Oracle Java SE 11.0.27: upgrade to Java 11.0.28 or later
  4. For Oracle Java SE 17.0.15: upgrade to Java 17.0.16 or later
  5. For Oracle Java SE 21.0.7: upgrade to Java 21.0.8 or later
  6. For Oracle Java SE 24.0.1: upgrade to Java 24.0.2 or later
  7. For Oracle GraalVM for JDK 17.0.15: upgrade to GraalVM for JDK 17.0.16 or later
  8. For Oracle GraalVM for JDK 21.0.7: upgrade to GraalVM for JDK 21.0.8 or later
Caveat Standard Oracle CPU upgrade - backward compatible; verify application compatibility in non-production environment before deploying to production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jre Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-50059 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-50059 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data