dbcve.org
JreApplication · Oracle

CVE-2025-50106

HIGH · 8.1 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 →
90/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: 2D). Supported versions that are affected are Oracle Java SE: 8u451, 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. 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 takeover of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. 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 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H).

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

Buffer overflow or similar memory corruption vulnerability in Java SE's 2D graphics component (libawt.so) allows remote unauthenticated attackers to achieve arbitrary code execution and complete system compromise. The vulnerability is difficult to exploit due to complexity requirements but requires no authentication and can be triggered through web services or untrusted code (applets/Web Start).

MitigationApply Oracle Critical Patch Updates (CPU) for the affected Java versions. Upgrade to patched versions: Java SE 8u461+, 11.0.25+, 17.0.21+, 21.0.9+, 24.0.5+ or later. For GraalVM, upgrade to corresponding patched releases.

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

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

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 version
    Run 'java -version' or 'javac -version' to determine the exact Java version installed. For JDK installations, check $JAVA_HOME/release file.
    Affected if The installed version matches one of the affected versions: 1.8.0, 11.0.27, 17.0.15, 21.0.7, 24.0.1, or 21.3.14 (for GraalVM).
  2. Verify Java vendor and product type
    Run 'java -verbose' or check $JAVA_HOME to confirm whether the installation is Oracle JRE, Oracle JDK, or Oracle GraalVM. Some systems may have OpenJDK builds which have separate patch cycles.
    Affected if The installed product is Oracle JRE, Oracle JDK, or Oracle GraalVM matching the affected versions listed.
  3. Confirm 2D graphics library presence
    Locate libawt.so in the Java installation: find $JAVA_HOME -name 'libawt.so' 2>/dev/null. This library is required for the vulnerability to be present.
    Affected if libawt.so exists in the Java installation directory, indicating the vulnerable 2D graphics component is present.
  4. Check for applet or Web Start configuration
    Inspect Java Control Panel settings or check java.security.policy files for applet/Web Start enablement. Review deployment.properties in $JAVA_HOME/lib/deployment or user home .java/deployment.
    Affected if Java Web Start (javaws) or applet support is enabled, which provides an attack vector for triggering the vulnerability through untrusted code.
  5. Assess exposure to untrusted code execution
    Review whether the Java installation runs untrusted code from external sources, hosts web services processing untrusted input, or has the Security Manager disabled (common in modern deployments). Check for exposed Java RMI endpoints or similar interfaces.
    Affected if The system processes untrusted Java code, hosts web services accepting Java serialized objects, or runs Java applications with reduced security sandboxing.

You are affected if your Oracle Java installation (JRE, JDK, or GraalVM) matches version 1.8.0, 11.0.27, 17.0.15, 21.0.7, 24.0.1, or 21.3.14 AND the libawt.so 2D graphics component is present AND the system can execute untrusted code through applets, Web Start, or exposed web services.

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 Oracle Critical Patch Updates (CPU) for the affected Java versions. Upgrade to patched versions: Java SE 8u461+, 11.0.25+, 17.0.21+, 21.0.9+, 24.0.5+ or later. For GraalVM, upgrade to corresponding patched releases.

Recommended fix Moderate confidence

Oracle JDK 8u461+/11.0.25+/17.0.21+/21.0.5+ or latest Oracle Critical Patch Update release (October 2025)

  1. Identify the current installed Java/JDK version using 'java -version' or 'java -fullversion'
  2. Determine if the installed version matches one of the affected versions: JDK/JRE 1.8.0, 11.0.27, 17.0.15, 21.0.7 or GraalVM versions 17.0.15, 21.0.7, 24.0.1, 21.3.14
  3. Download the latest Oracle JDK from the official Oracle website (https://www.oracle.com/java/technologies/downloads/) or your organization's Java distribution channel
  4. For Oracle Java SE 8.x users: Upgrade to JDK 8u461 or later
  5. For Oracle Java SE 11.x users: Upgrade to JDK 11.0.25 or later
  6. For Oracle Java SE 17.x users: Upgrade to JDK 17.0.21 or later
  7. For Oracle Java SE 21.x users: Upgrade to JDK 21.0.5 or later
  8. For GraalVM for JDK users: Upgrade to a version containing the October 2025 CPU fixes
Caveat Upgrading JDK versions may introduce breaking changes in application code; regression testing is recommended, especially when moving between major versions like Java 8 to 11 or 17 to 21

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

Fix this in Jre Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing16.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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