dbcve.org
JreApplication · Oracle

CVE-2025-30698

MEDIUM · 5.6 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 →
65/100
Remediation priority · Elevated
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: 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 update, insert or delete access to some of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data as well as unauthorized read access to a subset of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data and unauthorized ability to cause a partial denial of service (partial DOS) 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 5.6 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L).

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 · moderate confidence

A vulnerability in the Java SE 2D component allows unauthenticated attackers with network access to compromise Java deployments that run untrusted code (sandboxed applets or Web Start applications). Successful exploitation can result in unauthorized read and write access to a subset of accessible data, plus partial denial of service. The attack is characterized as difficult to exploit.

MitigationApply Oracle's latest Critical Patch Update for the affected Java versions. Additionally, ensure Java deployments do not run untrusted code from the internet, or configure the security sandbox to only load code from trusted sources.

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
Low
Integrity
Low
Availability
Low

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

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 product and version
    Run 'java -version' to see the version string. Check if it shows 'Java(TM)' or 'Oracle' to confirm Oracle Java. For GraalVM, run 'java -version' and also check 'java -version' output for GraalVM indicators, or run 'java -Xinternal:version' for detailed build info.
    Affected if The version output matches one of the affected versions: 1.8.0, 11.0.26, 17.0.14, 21.0.6, 24 for Oracle JRE/JDK; 17.0.14, 21.0.6, 24 for Oracle GraalVM for JDK; 20.3.17 or 21.3.13 for Oracle GraalVM.
  2. Confirm Oracle Java distribution
    Run 'java -version' and examine the vendor line. Oracle Java typically shows 'Oracle Corporation' or contains 'Oracle' in the version output. OpenJDK builds show 'OpenJDK' instead.
    Affected if The vendor is Oracle or the version string explicitly references Oracle Java, since this vulnerability affects only Oracle Java distributions.
  3. Determine if 2D component is in use
    The Java 2D component is part of the standard Java runtime. Check if any Java applications use java.awt or javax.imageio packages by reviewing application code or dependencies. The 2D subsystem is loaded when any graphical Java application runs.
    Affected if The environment runs any Java application that loads the 2D subsystem (any application using AWT or Java 2D graphics), which is part of the standard Java SE installation.
  4. Check if untrusted code execution is possible
    Review whether the Java deployment runs sandboxed applets (via browser plugin) or Web Start applications. Check browser configurations, Java Control Panel settings (if available), and deployment descriptors for applet or JNLP configurations.
    Affected if The system runs or has the capability to run untrusted code through sandboxed applets or Web Start applications loaded from the network.

You are affected only if you run Oracle Java (or Oracle GraalVM) at one of the affected versions listed, and your deployment executes untrusted code via applets or Web Start applications using the Java 2D component.

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's latest Critical Patch Update for the affected Java versions. Additionally, ensure Java deployments do not run untrusted code from the internet, or configure the security sandbox to only load code from trusted sources.

Recommended fix High confidence

Upgrade to the next available CPU (Critical Patch Update) release: Java 8u451+, Java 11.0.27+, Java 17.0.15+, Java 21.0.7+, Java 24.0.1+; GraalVM for JDK 17.0.15+, 21.0.7+, 24.0.1+; GraalVM Enterprise Edition 20.3.18+, 21.3.14+

  1. Identify the currently installed Java/JDK version using 'java -version' or 'java --version'
  2. Identify the installed GraalVM version using 'graalvm --version' if applicable
  3. For Oracle Java SE 8u441: upgrade to Java 8u451 or later
  4. For Oracle Java SE 11.0.26: upgrade to Java 11.0.27 or later
  5. For Oracle Java SE 17.0.14: upgrade to Java 17.0.15 or later
  6. For Oracle Java SE 21.0.6: upgrade to Java 21.0.7 or later
  7. For Oracle Java SE 24: upgrade to Java 24.0.1 or later
  8. For GraalVM for JDK 17.0.14: upgrade to GraalVM for JDK 17.0.15 or later
Caveat Minor risk: Upgrading between major versions (e.g., 17 to 21) may introduce compatibility issues with older libraries; ensure application testing is performed before production deployment

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

Fix this in Jre Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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