dbcve.org
JreApplication · Oracle

CVE-2025-21587

HIGH · 7.4 CVSS v3.1 Published 2025-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
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: JSSE). Supported versions that are affected are Oracle Java SE:8u441, 8u441-perf, 11.0.26, 17.0.14, 21.0.6, 24; Oracle GraalVM for JDK:17.0.14, 21.0.6, 24; Oracle GraalVM Enterprise Edition:20.3.17 and 21.3.13. Difficult to exploit 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 as well as 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 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.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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

This is a vulnerability in Oracle Java SE's JSSE (Java Secure Socket Extension) component that handles SSL/TLS connections. The flaw allows an unauthenticated remote attacker with network access to potentially create, delete, or modify critical data, as well as access or fully control all accessible data through the Java deployment. Difficult to exploit due to high attack complexity, but requires no authentication.

MitigationApply the relevant Oracle Critical Patch Update for CVE-2025-21587, which involves upgrading to a patched version of Oracle Java SE, Oracle GraalVM for JDK, or Oracle GraalVM Enterprise Edition beyond the affected versions listed.

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.26= 17.0.14= 21.0.6= 24
JdkApplication
Affected:= 1.8.0= 11.0.26= 17.0.14= 21.0.6= 24
Graalvm For JdkApplication
Affected:= 17.0.14= 21.0.6= 24
GraalvmApplication
Affected:= 20.3.17= 21.3.13

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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 runtime version
    Run `java -version` or `java -fullversion` from command line. Note the full version string including update number (e.g., 1.8.0_401, 11.0.26, 17.0.14).
    Affected if The version exactly matches 1.8.0, 11.0.26, 17.0.14, 21.0.6, or 24 (for JRE or JDK).
  2. Confirm Java vendor is Oracle
    The `java -version` output includes the vendor (Oracle Corporation, Oracle OpenJDK, etc.). This CVE affects only Oracle Java SE implementations.
    Affected if Vendor is Oracle or Oracle OpenJDK and version matches affected list.
  3. Check for GraalVM installation
    Run `graalvm --version` if GraalVM is installed. Look for version such as 20.3.17, 21.3.13, or versions in the 17.x/21.x/24.x family.
    Affected if GraalVM for JDK or Oracle GraalVM version matches 20.3.17, 21.3.13, 17.0.14, 21.0.6, or 24.
  4. Verify JSSE is in use
    Confirm the Java application uses JSSE for SSL/TLS. This is the default Java SSL/TLS implementation. Check application configuration for javax.net.ssl properties or SSLContext usage.
    Affected if Application uses Java SSL/TLS connections (default behavior for most Java network applications).

You are affected if you run Oracle Java SE (JDK/JRE), Oracle GraalVM for JDK, or Oracle GraalVM with a version matching exactly 1.8.0, 11.0.26, 17.0.14, 21.0.6, 24, 20.3.17, or 21.3.13 and the system accepts network connections.

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

Apply the relevant Oracle Critical Patch Update for CVE-2025-21587, which involves upgrading to a patched version of Oracle Java SE, Oracle GraalVM for JDK, or Oracle GraalVM Enterprise Edition beyond the affected versions listed.

Recommended fix Moderate confidence

Oracle Java SE 8u451+, 11.0.27+, 17.0.15+, 21.0.7+, 24.0.1+ | OpenJDK equivalents | GraalVM for JDK 17.0.15+, 21.0.7+, 24.0.1+ | GraalVM Enterprise 20.3.18+, 21.3.14+

  1. Identify the currently installed Java/JDK version using 'java -version' or 'java -fullversion'
  2. For Oracle Java SE: Download and install the patched version from Oracle's official Java SE downloads page (oracle.com/java/technologies/downloads)
  3. For OpenJDK: Update via system package manager (e.g., 'apt update && apt install openjdk-17-jdk' on Debian/Ubuntu, 'yum update java-17-openjdk' on RHEL/CentOS)
  4. For GraalVM: Download the patched release from GraalVM's official distribution (graalvm.org/downloads)
  5. After installation, verify the fix by running 'java -version' and confirming the version number matches or exceeds the fixed release
  6. Restart any running Java applications to ensure they use the updated JVM
  7. If using Docker, rebuild containers with the updated base images containing the patched JDK
Caveat Upgrading JDK versions may require testing of application compatibility, especially when moving between major versions (e.g., 17 to 21 or 21 to 24); some APIs deprecated in newer versions may be removed

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

Fix this in Jre Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing24.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,520
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-21587 — 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-21587 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