GraalvmApplication · Oracle

CVE-2025-53066

HIGH · 7.5 CVSS v3.1 Published 2025-10-21

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

84/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: JAXP). Supported versions that are affected are Oracle Java SE: 8u461, 8u461-perf, 11.0.28, 17.0.16, 21.0.8, 25; Oracle GraalVM for JDK: 17.0.16 and 21.0.8; Oracle GraalVM Enterprise Edition: 21.3.15. 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. 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 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.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).

Technical summary

dbcve analysis · high confidence

This is a vulnerability in the JAXP (Java API for XML Processing) component of Oracle Java SE, Oracle GraalVM for JDK, and Oracle GraalVM Enterprise Edition. The vulnerability allows an unauthenticated attacker with network access to compromise the system through APIs that process XML data, potentially granting unauthorized access to critical or all accessible data. The CVSS vector indicates Confidentiality-only impact (C:H) with network exploitation, no privileges required, and no user interaction needed.

MitigationUpgrade Oracle Java SE, Oracle GraalVM for JDK, or Oracle GraalVM Enterprise Edition to versions beyond the affected releases (8u461, 11.0.28, 17.0.16, 21.0.8, 25). For Java Web Start or applet deployments, ensure the sandbox security settings are maintained and consider disabling these deprecated technologies if not needed.

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

Affected products & versions

NVD · CPE data

GraalvmApplication

Affected:= 21.3.15

Graalvm For JdkApplication

Affected:= 17.0.16= 21.0.8

JdkApplication

Affected:= 1.8.0= 11.0.28= 17.0.16= 21.0.8= 25

JreApplication

Affected:= 1.8.0= 11.0.28= 17.0.16= 21.0.8= 25

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

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

Am I affected?

dbcve checks

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

Identify installed Java version

Run `java -version` from command line or check JAVA_HOME environment variable and inspect the version-release file in that directory

Affected if The version matches Oracle JDK/JRE 1.8.0, 11.0.28, 17.0.16, 21.0.8, or 25; or Oracle GraalVM 21.3.15, 17.0.16, or 21.0.8
Confirm Oracle Java implementation

Check the vendor or distribution name via `java -verbose` or examine the installation directory for Oracle-specific licensing and binaries

Affected if The JDK/JRE is Oracle-branded rather than OpenJDK or alternative distributions
Verify JAXP XML processing is in use

Review application code or dependencies for imports from javax.xml.parsers, org.w3c.dom, org.xml.sax, or javax.xml.stream, indicating XML data processing

Affected if The application or service processes XML data from network sources using JAXP APIs
Assess network exposure of XML-processing endpoints

Review firewall rules, listening services, and application endpoints that accept XML input over network protocols (HTTP, SOAP, REST with XML payloads)

Affected if The system accepts untrusted XML input over the network on exposed APIs or services

A user is affected if they run any of the listed Oracle JDK/JRE or GraalVM versions AND have network-accessible applications or services that process XML data using JAXP APIs.

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

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Upgrade Oracle Java SE, Oracle GraalVM for JDK, or Oracle GraalVM Enterprise Edition to versions beyond the affected releases (8u461, 11.0.28, 17.0.16, 21.0.8, 25). For Java Web Start or applet deployments, ensure the sandbox security settings are maintained and consider disabling these deprecated technologies if not needed.

Recommended fix Moderate confidence

Oracle Java SE 8u481+/11.0.25+/17.0.21+/21.0.5+/25.0.2+ or GraalVM for JDK 17.0.21+/21.0.5+ or GraalVM Enterprise Edition 21.3.17+

1. Identify the currently installed Java/GraalVM version by running 'java -version' or checking the GraalVM installation
2. For Oracle Java SE 8u461: upgrade to Oracle Java SE 8u481 or later
3. For Oracle Java SE 11.0.28: upgrade to Oracle Java SE 11.0.25 or later
4. For Oracle Java SE 17.0.16: upgrade to Oracle Java SE 17.0.21 or later
5. For Oracle Java SE 21.0.8: upgrade to Oracle Java SE 21.0.5 or later
6. For Oracle Java SE 25: upgrade to Oracle Java SE 25.0.2 or later
7. For Oracle GraalVM for JDK 17.0.16: upgrade to GraalVM for JDK 17.0.21 or later
8. For Oracle GraalVM for JDK 21.0.8: upgrade to GraalVM for JDK 21.0.5 or later

Caveat Standard quarterly security updates; no API changes expected for this JAXP vulnerability fix

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

Fix this in Graalvm Scoped from the published advisory

Consultation2.0 h
Implementation4.0 h
Testing8.0 h
Review / QA2.0 h

16.0 hours of engineering $2,680

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2025-53066?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 7.5 High

Exploit likelihood EPSS, next 30 days 0.6%

Affects: Graalvm

Remediation

A high-priority fix

Fix this in Graalvm 16 hrs · Moderate

Typical engagement from $2,680

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2025-53066 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References