VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

mercury: vulnerability history, versions and safety

mercury is a package in the PyPI ecosystem. Vulert records 3 vulnerabilities for it across 98 releases, first recorded in Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded C2 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 19 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mercury vulnerabilities

Vulert verdict on mercury 3.2.11 i

Updated on 23 Oct 2026

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

Package health score 66/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release 3.2.11 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 3 in the last year i
  • Latest disclosure 19 Oct 2026 i
  • Highest CVSS 10.0 i
  • With no published fix 0 i
  • Stars 4,356 i
  • OpenSSF scorecard 3/10 i
  • Last release 1 month ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by PyPI, 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 mercury, 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
3.2.11 10 Sep 2026 none non-standard — Details →
3.2.10 04 Sep 2026 M1 non-standard Yes Details →
3.2.9 04 Sep 2026 M1 non-standard Yes Details →
3.2.8 03 Sep 2026 M1 non-standard Yes Details →
3.2.7 01 Sep 2026 M1 non-standard Yes Details →
3.2.6 28 Aug 2026 M1 non-standard Yes Details →
3.2.5 27 Aug 2026 C1 M1 non-standard Yes Details →
3.2.4 21 Aug 2026 C1 M1 non-standard Yes Details →
3.2.3 08 Jul 2026 C2 M1 non-standard Yes Details →
3.2.2 18 Jun 2026 C2 M1 non-standard Yes Details →
3.2.1 09 Jun 2026 C2 M1 non-standard Yes Details →
3.2.0 29 May 2026 C2 M1 non-standard Yes Details →
3.1.5 28 May 2026 C2 M1 non-standard Yes Details →
3.1.4 27 May 2026 C2 M1 non-standard Yes Details →
3.1.2 22 May 2026 C2 M1 non-standard Yes Details →
3.1.1 18 May 2026 C2 M1 non-standard Yes Details →
3.1.0 04 May 2026 C2 M1 non-standard Yes Details →
3.0.2 17 Apr 2026 C2 M1 non-standard Yes Details →
3.0.1 10 Apr 2026 C2 M1 non-standard Yes Details →
3.0.0 15 Jan 2026 C2 M1 non-standard Yes Details →
3.0.0rc1 14 Jan 2026 C1 non-standard Yes Details →
3.0.0b6 13 Jan 2026 C1 non-standard Yes Details →
3.0.0b5 12 Jan 2026 C1 non-standard Yes Details →
3.0.0b4 12 Jan 2026 C1 non-standard Yes Details →
3.0.0b3 12 Jan 2026 C1 non-standard Yes Details →
3.0.0b2 09 Jan 2026 C1 non-standard Yes Details →
3.0.0b1 31 Dec 2025 C1 non-standard Yes Details →
3.0.0a12 17 Dec 2025 C1 non-standard Yes Details →
3.0.0a11 16 Dec 2025 C1 non-standard Yes Details →
3.0.0a10 15 Dec 2025 C1 non-standard Yes Details →
3.0.0a9 11 Dec 2025 C1 non-standard Yes Details →
3.0.0a8 11 Dec 2025 C1 non-standard Yes Details →
3.0.0a7 10 Dec 2025 C1 non-standard Yes Details →
3.0.0a6 10 Dec 2025 C1 non-standard Yes Details →
3.0.0a5 10 Dec 2025 C1 non-standard Yes Details →
3.0.0a4 03 Dec 2025 C1 non-standard Yes Details →
3.0.0a3 03 Dec 2025 C1 non-standard Yes Details →
3.0.0a2 21 Nov 2025 C1 non-standard Yes Details →
3.0.0a1 20 Nov 2025 C1 non-standard Yes Details →
2.4.3 08 Jul 2024 C1 — Yes Details →
2.4.2 10 May 2024 C1 — Yes Details →
2.4.1 08 May 2024 C1 — Yes Details →
2.4.0 08 May 2024 C1 — Yes Details →
2.3.10 20 Mar 2024 C1 — Yes Details →
2.3.9 20 Mar 2024 C1 — Yes Details →
2.3.8 18 Mar 2024 C1 — Yes Details →
2.3.7 26 Oct 2023 C1 — Yes Details →
2.3.6 13 Oct 2023 C1 — Yes Details →
2.3.5 11 Oct 2023 C1 — Yes Details →
2.3.4 10 Aug 2023 C1 — Yes Details →
2.3.3 10 Aug 2023 C1 — Yes Details →
2.3.2 07 Aug 2023 C1 — Yes Details →
2.3.1 05 Jun 2023 C1 — Yes Details →
2.3.0 23 May 2023 C1 — Yes Details →
2.2.9 28 Apr 2023 C1 — Yes Details →
2.2.8 27 Apr 2023 C1 — Yes Details →
2.2.7 25 Apr 2023 C1 — Yes Details →
2.2.6 21 Apr 2023 C1 — Yes Details →
2.2.5 21 Apr 2023 C1 — Yes Details →
2.2.4 20 Apr 2023 C1 — Yes Details →
2.2.3 20 Apr 2023 C1 — Yes Details →
2.2.2 20 Apr 2023 C1 — Yes Details →
2.2.1 12 Apr 2023 C1 — Yes Details →
2.2.0 07 Apr 2023 C1 — Yes Details →
2.1.9 03 Apr 2023 C1 — Yes Details →
2.1.8 03 Apr 2023 C1 — Yes Details →
2.1.7 31 Mar 2023 C1 — Yes Details →
2.1.6 31 Mar 2023 C1 — Yes Details →
2.1.5 31 Mar 2023 C1 — Yes Details →
2.1.4 31 Mar 2023 C1 — Yes Details →
2.1.3 31 Mar 2023 C1 — Yes Details →
2.1.2 03 Mar 2023 C1 — Yes Details →
2.1.1 01 Mar 2023 C1 — Yes Details →
2.1.0 01 Mar 2023 C1 — Yes Details →
2.0.12 24 Feb 2023 C1 — Yes Details →
2.0.11 24 Feb 2023 C1 — Yes Details →
2.0.10 21 Feb 2023 C1 — Yes Details →
2.0.9 20 Feb 2023 C1 — Yes Details →
2.0.8 17 Feb 2023 C1 — Yes Details →
2.0.7 17 Feb 2023 C1 — Yes Details →
2.0.6 16 Feb 2023 C1 — Yes Details →
2.0.5 16 Feb 2023 C1 — Yes Details →
2.0.4 15 Feb 2023 C1 — Yes Details →
2.0.3 15 Feb 2023 C1 — Yes Details →
2.0.2 15 Feb 2023 C1 — Yes Details →
2.0.1 14 Feb 2023 C1 — Yes Details →
2.0.0 13 Feb 2023 C1 — Yes Details →
1.99.10 09 Feb 2023 C1 — Yes Details →
1.99.9 09 Feb 2023 C1 — Yes Details →
1.99.8 06 Feb 2023 C1 — Yes Details →
1.99.7 02 Feb 2023 C1 — Yes Details →
1.99.6 02 Feb 2023 C1 — Yes Details →
1.99.5 02 Feb 2023 C1 — Yes Details →
1.99.4 01 Feb 2023 C1 — Yes Details →
1.99.3 31 Jan 2023 C1 — Yes Details →
1.99.2 31 Jan 2023 C1 — Yes Details →
1.99.1 31 Jan 2023 C1 — Yes Details →
1.99.0 31 Jan 2023 C1 — Yes Details →
1.1.6 15 Dec 2022 C1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for mercury

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-111057: Mercury Unauthenticated Remote Code Execution via API Terminals Access Control Bypass 10.0 critical 3.2.4 19 Oct 2026
CVE-2026-111058: Mercury Unauthenticated Remote Code Execution via /api/kernels 9.8 critical 3.2.6 19 Oct 2026
CVE-2026-111059: Mercury Package Vulnerability Leading to Stored/DOM XSS via Untrusted Markdown Content 6.1 medium 3.2.11 19 Oct 2026

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 mercury

Is mercury safe to use?

Vulert records 3 vulnerabilities for mercury in PyPI: 2 critical, 0 high, 1 medium and 0 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 mercury's Vulert package health score?

Vulert scores mercury 66/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 mercury affected?

No. 3.2.11, 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 mercury should I use?

3.2.11 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 mercury have?

3 vulnerabilities are recorded for mercury in the PyPI ecosystem: 2 critical, 0 high, 1 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 mercury vulnerabilities disclosed?

3 vulnerabilities were recorded for mercury in the last 12 months, and the oldest entry in this database dates to 19 Oct 2026. 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 mercury 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 mercury for upcoming vulnerabilities?

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