VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

py-mini-racer: vulnerability history, versions and safety

py-mini-racer is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 21 releases, first recorded in Sep 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all py-mini-racer vulnerabilities

Vulert verdict on py-mini-racer 0.6.0 i

Updated on 23 Oct 2026

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

Package health score 60/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Widely used
  • Community Quiet

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

  • Current release 0.6.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 18 Sep 2020 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 230 packages i
  • Stars 769 i
  • OpenSSF scorecard 2/10 i
  • Last release 66 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 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 py-mini-racer, 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
0.6.0 22 Apr 2021 none non-standard — Details →
0.5.0 25 Feb 2021 none non-standard — Details →
0.5.0b2 10 Feb 2021 none non-standard — Details →
0.5.0b1 02 Oct 2020 none non-standard — Details →
0.4.0 22 Sep 2020 none non-standard — Details →
0.3.0 29 Jun 2020 none non-standard — Details →
0.2.0 11 Mar 2020 H1 U1 non-standard Yes Details →
0.2.0b2 09 Jan 2020 H1 U1 non-standard Yes Details →
0.2.0b1 09 Jan 2020 H1 U1 non-standard Yes Details →
0.1.18 07 Nov 2019 H1 U1 non-standard Yes Details →
0.1.17 19 Dec 2018 H1 U1 non-standard Yes Details →
0.1.15 18 Jun 2018 H1 U1 non-standard Yes Details →
0.1.14 25 May 2018 H1 U1 non-standard Yes Details →
0.1.13 16 Mar 2018 H1 U1 non-standard Yes Details →
0.1.12 04 Dec 2017 H1 U1 non-standard Yes Details →
0.1.11 21 Jul 2017 H1 U1 non-standard Yes Details →
0.1.10 31 Mar 2017 H1 U1 non-standard Yes Details →
0.1.9 24 Mar 2017 H1 U1 non-standard Yes Details →
0.1.8 02 Mar 2017 H1 U1 non-standard Yes Details →
0.1.7 05 Oct 2016 H1 U1 non-standard Yes Details →
0.1.6 12 Aug 2016 H1 U1 non-standard Yes Details →
0.1.5 04 Aug 2016 H1 U1 non-standard Yes Details →
0.1.5.dev0 04 Aug 2016 H1 U1 non-standard Yes Details →
0.1.4 04 Aug 2016 H1 U1 non-standard Yes Details →
0.1.3 04 Aug 2016 H1 U1 non-standard Yes Details →
0.1.2 03 Aug 2016 H1 U1 non-standard Yes Details →
0.1.1 02 Aug 2016 H1 U1 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 2

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

03 Vulnerabilities

Recorded vulnerabilities for py-mini-racer

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-25489: Heap Overflow in PyMiniRacer 9.8 high 0.3.0 18 Sep 2020
CVE-2020-25489: Heap Overflow in py-mini-racer N/A unrated 0.3.0 17 Sep 2020

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 py-mini-racer

Is py-mini-racer safe to use?

Vulert records 2 vulnerabilities for py-mini-racer in PyPI: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is py-mini-racer's Vulert package health score?

Vulert scores py-mini-racer 60/100, which reads as usable, but worth attention. 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 py-mini-racer affected?

No. 0.6.0, 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 py-mini-racer should I use?

0.6.0 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 py-mini-racer have?

2 vulnerabilities are recorded for py-mini-racer in the PyPI ecosystem: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new py-mini-racer vulnerabilities disclosed?

0 vulnerabilities were recorded for py-mini-racer in the last 12 months, and the oldest entry in this database dates to 17 Sep 2020. 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 py-mini-racer 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 py-mini-racer for upcoming vulnerabilities?

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