VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.mozilla:rhino: vulnerability history, versions and safety

org.mozilla:rhino is a package in the Maven ecosystem. Vulert records 1 vulnerability for it across 18 releases, first recorded in Dec 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 03 Dec 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all org.mozilla:rhino vulnerabilities

Vulert verdict on org.mozilla:rhino 1.9.1 i

Updated on 23 Oct 2026

Good news: 1.9.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 89/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Not enough data

What to do: Stay on 1.9.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.9.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 1.9.1 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 03 Dec 2025 i
  • Highest CVSS 2.7 i
  • With no published fix 0 i
  • Depended on by 239 packages i
  • Last release 8 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by Maven Central, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for org.mozilla:rhino, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.9.1 15 Feb 2026 none non-standard — Details →
1.9.0 22 Dec 2025 none non-standard — Details →
1.7.14.1 03 Dec 2025 none non-standard — Details →
1.7.15.1 03 Dec 2025 none non-standard — Details →
1.8.1 03 Dec 2025 none non-standard — Details →
1.8.0 03 Jan 2025 none non-standard — Details →
1.7.15 04 May 2024 none non-standard — Details →
1.7.14 06 Jan 2022 L1 non-standard Yes Details →
1.7.14-RC1 18 Nov 2021 L1 non-standard Yes Details →
1.7.13 02 Sep 2020 L1 non-standard Yes Details →
1.7.12 13 Jan 2020 L1 non-standard Yes Details →
1.7.11 30 May 2019 L1 non-standard Yes Details →
1.7.11-RC2 20 May 2019 L1 non-standard Yes Details →
1.7.11-RC1 17 May 2019 L1 non-standard Yes Details →
1.7.10 10 Apr 2018 L1 non-standard Yes Details →
1.7.9 15 Mar 2018 L1 non-standard Yes Details →
1.7.8 23 Jan 2018 L1 non-standard Yes Details →
1.7.8-RC1 22 Dec 2017 L1 non-standard Yes Details →
1.7.7.2 24 Aug 2017 L1 non-standard Yes Details →
1.7.7.1 01 Feb 2016 L1 non-standard Yes Details →
1.7.7 17 Jun 2015 L1 non-standard Yes Details →
1.7.6 15 Apr 2015 L1 non-standard Yes Details →
1.7R5 30 Jan 2015 L1 non-standard Yes Details →
1.7R4 20 Jun 2012 L1 non-standard Yes Details →
1.7R3 20 Jul 2011 L1 non-standard Yes Details →

All 25 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for org.mozilla:rhino

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-66453: High CPU Usage and Potential DoS in org.mozilla:rhino Due to toFixed() Function 2.7 low 1.7.14.1 03 Dec 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About org.mozilla:rhino

Is org.mozilla:rhino safe to use?

Vulert records 1 vulnerabilities for org.mozilla:rhino in Maven: 0 critical, 0 high, 0 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is org.mozilla:rhino's Vulert package health score?

Vulert scores org.mozilla:rhino 89/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of org.mozilla:rhino affected?

No. 1.9.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of org.mozilla:rhino should I use?

1.9.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does org.mozilla:rhino have?

1 vulnerability is recorded for org.mozilla:rhino in the Maven ecosystem: 0 critical, 0 high, 0 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.mozilla:rhino vulnerabilities disclosed?

1 vulnerability was recorded for org.mozilla:rhino in the last 12 months, and the oldest entry in this database dates to 03 Dec 2025. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of org.mozilla:rhino are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor org.mozilla:rhino for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.mozilla:rhino version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.