GraalvmApplication · Oracle

CVE-2025-53057

MEDIUM · 5.9 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 →

68/100

Remediation priority · Elevated

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: Security). 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. 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. 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 5.9 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N).

Technical summary

dbcve analysis · high confidence

This is a vulnerability in Oracle Java SE's Security component affecting multiple versions (8u461 through 25, GraalVM variants). It allows unauthenticated remote attackers with network access to modify critical data through APIs or by tricking users into running untrusted code (applets/web start). The vulnerability has high integrity impact but requires high attack complexity and is difficult to exploit.

MitigationApply Oracle's latest Java SE security patches from the Critical Patch Update. For client-side deployments, ensure sandbox restrictions are enforced and avoid loading untrusted code from untrusted sources.

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/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` (or `java -version 2>&1` on some systems) to display the installed JRE/JDK version

Affected if The version displayed matches 1.8.0, 11.0.28, 17.0.16, 21.0.8, or 25 exactly (or falls within the 8u461 through 25 range)
Check if JDK is installed

Run `java -XshowSettings:properties -version 2>&1 | grep -i 'java.home'` to locate the Java installation directory, then check for the presence of a `jdk` folder versus a `jre` folder

Affected if A JDK is installed with version 1.8.0, 11.0.28, 17.0.16, 21.0.8, or 25 exactly
Check for Oracle GraalVM installation

Run `which java` and inspect the installation path, or run `java -version` and look for 'GraalVM' in the output

Affected if GraalVM version 21.3.15, or GraalVM for JDK versions 17.0.16 or 21.0.8 is installed
Verify Security component presence

Inspect the JRE/JDK lib directory for the presence of security-related JAR files (such as `jaas.jar`, `jce.jar`, or files in the `lib/security` folder) which contain the vulnerable component

Affected if The Security component JARs exist in a standard Oracle Java installation

The environment is affected if Oracle Java SE (JDK, JRE, or GraalVM) is installed with version exactly matching 1.8.0, 11.0.28, 17.0.16, 21.0.8, 21.3.15, or 25.

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

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Apply Oracle's latest Java SE security patches from the Critical Patch Update. For client-side deployments, ensure sandbox restrictions are enforced and avoid loading untrusted code from untrusted sources.

Recommended fix High confidence

Oracle Java SE 8u471+/11.0.25+/17.0.25+/21.0.5+ or GraalVM for JDK 17.0.25+/21.0.5+ or GraalVM Enterprise Edition latest

Identify the exact Oracle Java SE or GraalVM version currently installed using 'java -version' or checking the installation directory
For Oracle Java SE 8: Upgrade to Java 8u471 or later
For Oracle Java SE 11: Upgrade to Java 11.0.25 or later
For Oracle Java SE 17: Upgrade to Java 17.0.25 or later
For Oracle Java SE 21: Upgrade to Java 21.0.5 or later
For Oracle GraalVM for JDK 17: Upgrade to GraalVM for JDK 17.0.25 or later
For Oracle GraalVM for JDK 21: Upgrade to GraalVM for JDK 21.0.5 or later
For Oracle GraalVM Enterprise Edition 21.3.15: Upgrade to the latest Oracle GraalVM Enterprise Edition (contact Oracle for specific version)

Caveat Minor compatibility risks may exist for applications relying on specific previous behavior; test thoroughly before production deployment

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

Fix this in Graalvm Scoped from the published advisory

Consultation4.0 h
Implementation8.0 h
Testing12.0 h
Review / QA4.0 h

28.0 hours of engineering $4,760

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2025-53057 — 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-53057 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2025-53057?

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 5.9 Medium

Exploit likelihood EPSS, next 30 days 0.5%

Affects: Graalvm

Remediation

Need this fixed?

Fix this in Graalvm 28 hrs · Moderate

Typical engagement from $4,760

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2025-53057 and return a fixed quote.

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