JreApplication · Oracle

CVE-2025-30761

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

68/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Vulnerability in the Oracle Java SE, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Scripting). Supported versions that are affected are Oracle Java SE: 8u451, 8u451-perf and 11.0.27; 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 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 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 the Scripting component of Oracle Java SE (versions 8u451, 8u451-perf, 11.0.27) and Oracle GraalVM Enterprise Edition (21.3.14). It allows unauthenticated remote attackers to create, delete, or modify critical data through the scripting APIs, potentially via web services or untrusted code in sandboxed Java Web Start applications or applets. The CVSS 3.1 score of 5.9 reflects high integrity impact but with high attack complexity.

MitigationApply the latest Oracle security patches for the affected Java SE and GraalVM Enterprise Edition versions. For client-side deployments, ensure Java Web Start applications and applets are properly sandboxed and avoid loading untrusted code.

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

JreApplication

Affected:= 1.8.0= 11.0.27

JdkApplication

Affected:= 1.8.0= 11.0.27

GraalvmApplication

Affected:= 21.3.14

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 -fullversion' from command line to see the installed JRE/JDK version

Affected if The version shown is 8u451, 8u451-perf, or 11.0.27 for Oracle Java SE, or 21.3.14 for Oracle GraalVM Enterprise Edition
Check if using Oracle JDK or JRE

Run 'java -version' and verify the vendor is Oracle (not OpenJDK, AdoptOpenJDK, etc.) The output typically shows 'Java(TM)' or 'Oracle' in the vendor string

Affected if The vendor is Oracle and the version matches the affected versions listed in CVE-2025-30761
Identify GraalVM installation and version

If GraalVM is installed, run 'java -version' from the GraalVM home directory or check the 'java.runtime.version' system property. GraalVM typically shows 'GraalVM' in the version output

Affected if GraalVM Enterprise Edition version 21.3.14 is installed
Verify Scripting API is accessible

The Scripting API (javax.script) is part of standard Java SE. Check if the Java installation includes the 'jdk.scripting' module by running 'java --list-modules' and looking for 'jdk.scripting' or 'java.scripting'

Affected if The scripting module is present and the Java version is one of the affected versions
Check for Java Web Start or Applet usage

For desktop deployments, check if Java Web Start (javaws) or browser applets are enabled. On Windows, look for 'javaws.exe' in the Java installation path or check browser Java plugin settings

Affected if Java Web Start or applets are actively used and the Java version is vulnerable

A system is affected if it runs Oracle Java SE version 8u451, 8u451-perf, or 11.0.27, or Oracle GraalVM Enterprise Edition version 21.3.14, particularly if the Scripting API or Java Web Start is accessible to untrusted code.

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 the latest Oracle security patches for the affected Java SE and GraalVM Enterprise Edition versions. For client-side deployments, ensure Java Web Start applications and applets are properly sandboxed and avoid loading untrusted code.

Recommended fix Moderate confidence

Oracle Java SE 8u461+/11.0.25+ or Oracle GraalVM Enterprise Edition 21.3.15+

1. Identify the currently installed Java version using 'java -version' or 'java -fullversion'
2. For Oracle Java SE 8: upgrade to Oracle Java SE 8u461 or later (Critical Patch Update containing the fix)
3. For Oracle Java SE 11: upgrade to Oracle Java SE 11.0.25 or later
4. For Oracle GraalVM Enterprise Edition: upgrade to 21.3.15 or later
5. Verify the upgrade by running 'java -version' to confirm the new version is installed
6. Test that applications relying on the Java Scripting API function correctly after the upgrade

Caveat Major version upgrades (e.g., Java 8 to 11+) may introduce behavioral changes; test compatibility thoroughly before production deployment

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

Fix this in Jre Scoped from the published advisory

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

10.0 hours of engineering $1,780

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Notes0 Guidelines

Know something about CVE-2025-30761?

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

Affects: Jre

Remediation

Need this fixed?

Fix this in Jre 10 hrs · Moderate

Typical engagement from $1,780

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2025-30761 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