VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

mistralai: vulnerability history, versions and safety

mistralai is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 113 releases, first recorded in May 2026. 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 C2
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
2 in the last 12 months

Most recent disclosure 18 May 2026.

See the disclosure history →
i
1 malicious-package vulnerabilities

A published version contained malicious code.

See malicious packages in PyPI →

See all mistralai vulnerabilities

Vulert verdict on mistralai 3.3.0 i

Updated on 23 Oct 2026

Careful: 3.3.0 was published with malicious code in it, not just a bug. Do not install it.

Package health score 15/100
  • Security Malicious code published
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

The current release contains malicious code, which caps this score.

What to do: Do not resolve 3.3.0 as-is. Check whether you already run an affected release and pin a version the maintainers have re-published. Check what you run: Vulert alerts you when a safe version is published. Monitor it with Vulert →

  • Current release 3.3.0 — affected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 18 May 2026 i
  • Highest CVSS 9.6 i
  • With no published fix 2 i
  • Malicious packages 1 i
  • Depended on by 467 packages i
  • Stars 774 i
  • Last release this month i
  • Licence Apache-2.0 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 mistralai, 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.3.0 20 Oct 2026 C2 malicious — No Details →
3.2.0 09 Oct 2026 C2 malicious — No Details →
3.1.0 06 Oct 2026 C2 malicious — No Details →
3.0.0 28 Sep 2026 C2 malicious — No Details →
2.10.1 15 Sep 2026 C2 malicious — No Details →
2.10.0 09 Sep 2026 C2 malicious — No Details →
2.9.4 21 Aug 2026 C2 malicious — No Details →
2.9.3 13 Aug 2026 C2 malicious — No Details →
2.9.2 11 Aug 2026 C2 malicious — No Details →
2.9.1 04 Aug 2026 C2 malicious — No Details →
2.9.0 04 Aug 2026 C2 malicious — No Details →
2.8.0 28 Jul 2026 C2 malicious — No Details →
2.7.2 24 Jul 2026 C2 malicious — No Details →
2.7.1 21 Jul 2026 C2 malicious — No Details →
2.7.0 17 Jul 2026 C2 malicious — No Details →
2.6.0 06 Jul 2026 C2 malicious — No Details →
2.5.2 03 Jul 2026 C2 malicious — No Details →
2.5.1 01 Jul 2026 C2 malicious — No Details →
2.5.0 23 Jun 2026 C2 malicious — No Details →
2.4.13 19 Jun 2026 C2 malicious — No Details →
2.4.12 17 Jun 2026 C2 malicious — No Details →
2.4.11 16 Jun 2026 C2 malicious — No Details →
2.4.10 16 Jun 2026 C2 malicious — No Details →
2.4.9 03 Jun 2026 C2 malicious — No Details →
2.4.8 28 May 2026 C2 malicious — No Details →
2.4.7 25 May 2026 C2 malicious — No Details →
2.4.5 07 May 2026 C2 malicious — No Details →
2.4.4 30 Apr 2026 C2 malicious — No Details →
2.4.3 27 Apr 2026 C2 malicious — No Details →
2.4.2 23 Apr 2026 C2 malicious — No Details →
2.4.1 21 Apr 2026 C2 malicious — No Details →
2.4.0 16 Apr 2026 C2 malicious — No Details →
2.4.0rc2 14 Apr 2026 C2 malicious — No Details →
2.4.0rc1 14 Apr 2026 C2 malicious — No Details →
2.3.2 10 Apr 2026 C2 malicious — No Details →
2.3.1 07 Apr 2026 C2 malicious — No Details →
2.3.0 03 Apr 2026 C2 malicious — No Details →
2.2.0 31 Mar 2026 C2 malicious — No Details →
2.2.0rc3 30 Mar 2026 C2 malicious — No Details →
2.2.0rc2 30 Mar 2026 C2 malicious — No Details →
2.2.0rc1 30 Mar 2026 C2 malicious — No Details →
2.1.3 23 Mar 2026 C2 malicious — No Details →
2.1.2 20 Mar 2026 C2 malicious — No Details →
2.1.1 20 Mar 2026 C2 malicious — No Details →
2.1.0 20 Mar 2026 C2 malicious — No Details →
2.0.5 18 Mar 2026 C2 malicious — No Details →
2.0.4 16 Mar 2026 C2 malicious — No Details →
2.0.3 16 Mar 2026 C2 malicious — No Details →
2.0.2 13 Mar 2026 C2 malicious — No Details →
2.0.1 12 Mar 2026 C2 malicious — No Details →
2.0.0 10 Mar 2026 C2 malicious — No Details →
2.0.0rc1 02 Mar 2026 C2 malicious — No Details →
2.0.0b1 26 Feb 2026 C2 malicious — No Details →
1.12.4 20 Feb 2026 C2 malicious — No Details →
1.12.3 17 Feb 2026 C2 malicious — No Details →
1.12.2 13 Feb 2026 C2 malicious — No Details →
1.12.1 11 Feb 2026 C2 malicious — No Details →
1.12.0 04 Feb 2026 C2 malicious — No Details →
1.11.1 29 Jan 2026 C2 malicious — No Details →
1.10.1 16 Jan 2026 C2 malicious — No Details →
1.10.0 17 Dec 2025 C2 malicious — No Details →
1.9.11 02 Oct 2025 C2 malicious — No Details →
1.9.10 02 Sep 2025 C2 malicious — No Details →
1.9.9 26 Aug 2025 C2 malicious — No Details →
1.9.8 25 Aug 2025 C2 malicious — No Details →
1.9.7 20 Aug 2025 C2 malicious — No Details →
1.9.6 17 Aug 2025 C2 malicious — No Details →
1.9.3 23 Jul 2025 C2 malicious — No Details →
1.9.2 10 Jul 2025 C2 malicious — No Details →
1.9.1 01 Jul 2025 C2 malicious — No Details →
1.8.2 10 Jun 2025 C2 malicious — No Details →
1.8.1 28 May 2025 C2 malicious — No Details →
1.8.0 27 May 2025 C2 malicious — No Details →
1.7.1 22 May 2025 C2 malicious — No Details →
1.7.0 16 Apr 2025 C2 malicious — No Details →
1.6.0 21 Mar 2025 C2 malicious — No Details →
1.5.2 19 Mar 2025 C2 malicious — No Details →
1.5.2rc1 17 Mar 2025 C2 malicious — No Details →
1.5.1 06 Mar 2025 C2 malicious — No Details →
1.5.0 28 Jan 2025 C2 malicious — No Details →
1.4.0 21 Jan 2025 C2 malicious — No Details →
1.3.1 15 Jan 2025 C2 malicious — No Details →
1.3.0 14 Jan 2025 C2 malicious — No Details →
1.2.6 06 Jan 2025 C2 malicious — No Details →
1.2.5 04 Dec 2024 C2 malicious — No Details →
1.2.4 04 Dec 2024 C2 malicious — No Details →
1.2.3 18 Nov 2024 C2 malicious — No Details →
1.2.2 12 Nov 2024 C2 malicious — No Details →
1.2.1 08 Nov 2024 C2 malicious — No Details →
1.2.0 07 Nov 2024 C2 malicious — No Details →
1.1.0 17 Sep 2024 C2 malicious — No Details →
1.0.3 04 Sep 2024 C2 malicious — No Details →
1.0.2 22 Aug 2024 C2 malicious — No Details →
1.0.1 08 Aug 2024 C2 malicious — No Details →
1.0.0 07 Aug 2024 C2 malicious — No Details →
1.0.0rc2 06 Aug 2024 C2 malicious — No Details →
1.0.0rc1 01 Aug 2024 C2 malicious — No Details →
0.4.2 04 Jul 2024 C2 malicious Apache-2.0 No Details →
0.4.1 19 Jun 2024 C2 malicious — No Details →
0.4.0 05 Jun 2024 C2 malicious — No Details →
0.3.0 29 May 2024 C2 malicious — No Details →
0.2.0 23 May 2024 C2 malicious — No Details →
0.1.8 26 Mar 2024 C2 malicious — No Details →
0.1.7 26 Mar 2024 C2 malicious — No Details →
0.1.6 11 Mar 2024 C2 malicious — No Details →
0.1.3 26 Feb 2024 C2 malicious — No Details →
0.1.2 26 Feb 2024 C2 malicious — No Details →
0.0.12 29 Jan 2024 C2 malicious — No Details →
0.0.11 15 Jan 2024 C2 malicious — No Details →
0.0.10 15 Jan 2024 C2 malicious — No Details →
0.0.9 20 Dec 2023 C2 malicious — No Details →
0.0.8 11 Dec 2023 C2 malicious — No Details →
0.0.7 09 Dec 2023 C2 malicious — No Details →

All 113 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 2

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

03 Vulnerabilities

Recorded vulnerabilities for mistralai

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Malicious Dropper Vulnerability in mistralai Package Version 2.4.6 9.6 critical No fix published 18 May 2026
Critical Credential Theft Vulnerability in Mistralai Package N/A critical No fix published 12 May 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 mistralai

Is mistralai safe to use?

Vulert records 2 vulnerabilities for mistralai in PyPI: 2 critical, 0 high, 0 medium and 0 low. 2 of them have no published fix yet, so those are the ones to avoid or mitigate. 1 are malicious-package vulnerabilities: the published package itself contained hostile code, not only a bug.

What is mistralai's Vulert package health score?

Vulert scores mistralai 15/100, which reads as critical. 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). The current release contains malicious code, which caps this score.

Is the latest version of mistralai affected?

Yes. 3.3.0, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does mistralai have?

2 vulnerabilities are recorded for mistralai in the PyPI ecosystem: 2 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 mistralai vulnerabilities disclosed?

2 vulnerabilities were recorded for mistralai in the last 12 months, and the oldest entry in this database dates to 12 May 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 mistralai 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.

What does a malicious-package vulnerability mean?

It means the published package itself contained hostile code — a backdoor, a credential stealer or similar — rather than only a bug. Registries remove such packages once they are confirmed, so treat any application that resolved an affected version as compromised and rotate the credentials it could reach.

How do I monitor mistralai for upcoming vulnerabilities?

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