dbcve.org
RhinoApplication · Mozilla

CVE-2025-66453

HIGH · 7.5 CVSS v3.1 Published 2025-12-03
Fix available
A fix is available. Upgrade to 1.7.14.1 or later.
See remediation →
84/100
Remediation priority · High
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
Rhino is an open-source implementation of JavaScript written entirely in Java. Prior to 1.8.1, 1.7.15.1, and 1.7.14.1, when an application passed an attacker controlled float poing number into the toFixed() function, it might lead to high CPU consumption and a potential Denial of Service. Small numbers go through this call stack: NativeNumber.numTo > DToA.JS_dtostr > DToA.JS_dtoa > DToA.pow5mult where pow5mult attempts to raise 5 to a ridiculous power. This vulnerability is fixed in 1.8.1, 1.7.15.1, and 1.7.14.1.

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

Rhino (JavaScript in Java) contains a denial-of-service vulnerability in the toFixed() function where attacker-controlled floating-point numbers trigger excessive computation. The issue occurs in the DToA library's pow5mult function, which attempts to raise 5 to an extremely large power when processing certain float values, causing high CPU consumption.

MitigationUpgrade Rhino to version 1.8.1, 1.7.15.1, or 1.7.14.1 to patch the vulnerability. If immediate upgrade is not feasible, implement input validation or rate-limiting on toFixed() calls to reject unusually large or small float values.

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
RhinoApplication
Affected:< 1.7.14.1= 1.7.15= 1.8.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 Rhino installation
    Search for Rhino JAR files (rhino-*.jar) in your project dependencies (Maven pom.xml, Gradle build files, or lib directories) or locate the rhino package in your Java classpath
    Affected if Rhino library is present in your environment
  2. Determine Rhino version
    Locate the Rhino JAR file or dependency declaration and extract the version number. For Maven/Gradle, check the version in your dependency management. For direct JAR usage, examine the filename or MANIFEST.MF inside the JAR
    Affected if The installed version is less than 1.7.14.1, equal to 1.7.15, or equal to 1.8.0
  3. Identify toFixed() usage
    Search your codebase for calls to the JavaScript toFixed() method, particularly in code that executes user-provided JavaScript or processes floating-point numbers through Rhino's Nashorn or older ScriptEngine
    Affected if Your application invokes toFixed() on float or double values, especially with attacker-controlled input
  4. Check input source to toFixed()
    Review code paths where numeric values reach toFixed() - trace whether these values come from user input, API requests, or untrusted data sources that could contain specially crafted floating-point numbers
    Affected if Untrusted or user-controlled floating-point numbers can reach the toFixed() function

You are affected if Rhino version is < 1.7.14.1, = 1.7.15, or = 1.8.0 AND your application processes untrusted floating-point numbers through the toFixed() method.

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
Upgrade available Upgrade to 1.7.14.1 or later
Fixed in 1.7.14.1
Interim mitigation

Upgrade Rhino to version 1.8.1, 1.7.15.1, or 1.7.14.1 to patch the vulnerability. If immediate upgrade is not feasible, implement input validation or rate-limiting on toFixed() calls to reject unusually large or small float values.

Recommended fix High confidence

Rhino 1.8.1 (or 1.7.15.1 / 1.7.14.1 depending on branch)

  1. Identify the current Rhino version in use by checking project dependencies (Maven pom.xml, Gradle build.gradle, or JAR file metadata)
  2. Upgrade Rhino to version 1.8.1 (recommended), 1.7.15.1, or 1.7.14.1 depending on compatibility requirements
  3. For Maven projects: update the dependency in pom.xml to <version>1.8.1</version> for artifact org.mozilla:rhino
  4. For Gradle projects: update implementation 'org.mozilla:rhino:1.8.1' in build.gradle
  5. Rebuild and redeploy the application
  6. Verify the fix by testing the toFixed() function with small float values (e.g., 1e-300, 1e-320) to confirm no excessive CPU consumption occurs
Caveat Review release notes for any API changes between current version and target version; 1.8.x may have behavioral differences from 1.7.x

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

Fix this in Rhino Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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