dbcve.org
JreApplication · Oracle

CVE-2025-30749

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 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.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

Unauthenticated remote attacker can exploit a flaw in the Java SE 2D component to achieve complete system takeover. This is a sandbox escape vulnerability affecting Java Web Start applications and sandboxed applets that load untrusted code from the internet. The vulnerability is difficult to exploit (high complexity attack) but leads to full confidentiality, integrity, and availability compromise.

MitigationApply Oracle Critical Patch Updates for affected Java SE, GraalVM for JDK, or GraalVM Enterprise Edition versions. Disable or avoid running untrusted code in Java Web Start applications or applets until patches are applied.

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 Java/JRE/JDK installation
    Run 'java -version' or 'javac -version' to see the installed Java version and vendor. For Oracle installations, also check 'java -fullversion'.
    Affected if The installed version is an Oracle Java version prior to the fixed patch levels (1.8.0_441+, 11.0.27+, 17.0.15+, 21.0.7+, 24.0.1+) or is Oracle GraalVM prior to 21.3.14.
  2. Confirm Oracle Java vendor
    Check if the installed Java is from Oracle (not OpenJDK, Adoptium, or other distributions) by examining the vendor string from 'java -version' output or the Java control panel.
    Affected if The vendor is Oracle and the version falls within the affected range.
  3. Check for Java Web Start usage
    Look for .jnlp files on the system or check if Java Web Start (javaws) is installed and configured. Search for 'javaws' binary and .jnlp file associations.
    Affected if Java Web Start applications are deployed in the environment.
  4. Check for sandboxed applet usage
    Review browser configurations and Java settings for applet execution. Check Java Control Panel security settings for 'browser with Java plugin'.
    Affected if Browsers have Java plugin enabled or sandboxed applets are expected to run.
  5. Determine if untrusted code loading is possible
    Review Java security manager settings and whether applications load code from untrusted network sources. Check if code signing policies allow untrusted code execution.
    Affected if The Java environment permits loading untrusted code from the internet via Web Start or applets.

A user is affected if they run an Oracle Java/JDK/GraalVM version prior to the fixed versions AND have Java Web Start or sandboxed applets enabled that load untrusted code from the internet.

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 for affected Java SE, GraalVM for JDK, or GraalVM Enterprise Edition versions. Disable or avoid running untrusted code in Java Web Start applications or applets until patches are applied.

Recommended fix High confidence

July 2025 Oracle Critical Patch Update (CPU) - Java 8u461+/11.0.28+/17.0.16+/21.0.8+/24.0.2+, or GraalVM for JDK 17.0.16+/21.0.8+/24.0.2+, or GraalVM Enterprise Edition 21.3.15+

  1. 1. Identify the currently installed Java/JDK version using 'java -version' or checking the installation directory
  2. 2. For Oracle Java SE: Upgrade to the July 2025 CPU patch release that includes the fix for CVE-2025-30749
  3. 3. For Oracle GraalVM for JDK: Upgrade to version 17.0.16 or later, 21.0.8 or later, or 24.0.2 or later as appropriate for your major version line
  4. 4. For Oracle GraalVM Enterprise Edition: Upgrade to version 21.3.15 or later
  5. 5. Verify the upgrade by running 'java -version' and confirming the new version is loaded
  6. 6. Test your applications to ensure compatibility with the updated Java version
Caveat Upgrade follows standard Oracle CPU patching; minimal compatibility risk for patch releases, but test applications to verify full compatibility

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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