VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

murmurhash: vulnerability history, versions and safety

murmurhash is a package in the PyPI ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the PyPI ecosystem.

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 murmurhash vulnerabilities

Vulert verdict on murmurhash 1.1.0.dev0 i

Updated on 23 Oct 2026

Good news: 1.1.0.dev0, the version you would install today, has no known vulnerabilities.

Package health score 48/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Little adoption
  • Community Quiet

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

  • Current release 1.1.0.dev0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 47 i
  • OpenSSF scorecard 4/10 i
  • Last release 93 months ago i
  • Licence MIT 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 murmurhash, 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.0.15 14 Nov 2025 none MIT — Details →
1.0.14 12 Nov 2025 none MIT — Details →
1.0.13 22 May 2025 none MIT — Details →
1.0.12 16 Jan 2025 none MIT — Details →
1.0.11 22 Nov 2024 none MIT — Details →
1.0.10 15 Sep 2023 none MIT — Details →
1.0.9 14 Oct 2022 none MIT — Details →
1.0.8 15 Aug 2022 none MIT — Details →
1.0.7 26 Apr 2022 none MIT — Details →
1.0.7.dev0 17 Dec 2021 none MIT — Details →
1.0.6 22 Oct 2021 none MIT — Details →
1.0.5 07 Dec 2020 none MIT — Details →
1.0.4 02 Nov 2020 none MIT — Details →
1.0.3 02 Nov 2020 none MIT — Details →
1.0.2 18 Feb 2019 none MIT — Details →
1.0.2.dev0 18 Feb 2019 none MIT — Details →
1.1.0.dev0 17 Jan 2019 none MIT — Details →
1.0.1 30 Oct 2018 none MIT — Details →
1.0.0 13 Oct 2018 none MIT — Details →
1.0.0.dev0 15 Aug 2018 none MIT — Details →
0.28.0 01 Jun 2017 none MIT — Details →
0.26.4 30 Apr 2016 none MIT — Details →
0.26.3 16 Apr 2016 none MIT — Details →
0.26.2 25 Mar 2016 none MIT — Details →
0.26.1 19 Feb 2016 none MIT — Details →
0.26.0 21 Dec 2015 none MIT — Details →
0.25.0 21 Dec 2015 none MIT — Details →
0.24.0 04 Jan 2015 none — — Details →
0.23.0 04 Jan 2015 none — — Details →
0.22.0 04 Jan 2015 none — — Details →
0.21.0 03 Jan 2015 none — — Details →
0.20.0 02 Jan 2015 none — — Details →
0.19.0 02 Jan 2015 none — — Details →
0.18.0 02 Jan 2015 none — — Details →
0.17.0 31 Jul 2014 none — — Details →
0.16.0 30 Jul 2014 none — — Details →
0.15.0 30 Jul 2014 none — — Details →
0.14.0 30 Jul 2014 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for murmurhash

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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 murmurhash

Is murmurhash safe to use?

Vulert has no vulnerabilities on record for murmurhash in PyPI at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is murmurhash's Vulert package health score?

Vulert scores murmurhash 48/100, which reads as risky. 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 murmurhash affected?

No. 1.1.0.dev0, 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 murmurhash should I use?

1.0.15 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 murmurhash have?

0 vulnerabilities are recorded for murmurhash in the PyPI ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new murmurhash vulnerabilities disclosed?

0 vulnerabilities were recorded for murmurhash in the last 12 months. 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 murmurhash 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 murmurhash for upcoming vulnerabilities?

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