VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

mindsdb: vulnerability history, versions and safety

mindsdb is a package in the PyPI ecosystem. Vulert records 46 vulnerabilities for it across 120 releases, from Mar 2023 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
46 vulnerabilities recorded C1 H15 M6 L1 U23
i
15 with no fix published

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

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

Most recent disclosure 13 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mindsdb vulnerabilities

Vulert verdict on mindsdb 26.1.0 i

Updated on 23 Oct 2026

Careful: 26.1.0 has 17 known vulnerabilities, and 15 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 50/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 26.1.0 — affected i
  • Vulnerabilities on record 46 over 3 years · 10 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 9.3 i
  • With no published fix 15 i
  • Depended on by 1 packages i
  • Stars 39,801 i
  • OpenSSF scorecard 5/10 i
  • Last release 6 months ago i
  • Licence Elastic-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 mindsdb, 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
26.1.0 23 Apr 2026 U1 Elastic-2.0 No Details →
26.1.0rc1 17 Apr 2026 U1 Elastic-2.0 No Details →
26.0.1 03 Mar 2026 M1 U2 Elastic-2.0 No Details →
26.0.0 25 Feb 2026 M1 U2 Elastic-2.0 No Details →
26.0.0rc3 20 Feb 2026 M1 U2 Elastic-2.0 No Details →
26.0.0rc2 19 Feb 2026 M1 U2 Elastic-2.0 No Details →
26.0.0rc1 17 Feb 2026 M1 U2 Elastic-2.0 No Details →
25.14.1 21 Jan 2026 M1 L1 U3 Elastic-2.0 No Details →
25.14.0 19 Jan 2026 M1 L1 U3 Elastic-2.0 No Details →
25.14.0rc1 13 Jan 2026 M1 L1 U3 Elastic-2.0 No Details →
25.13.1 08 Jan 2026 M1 L1 U3 Elastic-2.0 No Details →
25.13.0 05 Jan 2026 M1 L1 U3 Elastic-2.0 No Details →
25.13.0rc2 16 Dec 2025 M1 L1 U3 Elastic-2.0 No Details →
25.13.0rc1 16 Dec 2025 M1 L1 U3 Elastic-2.0 No Details →
25.12.0 09 Dec 2025 M1 L1 U3 Elastic-2.0 No Details →
25.12.0rc1 05 Dec 2025 M1 L1 U3 Elastic-2.0 No Details →
25.11.1 03 Dec 2025 M1 L1 U3 Elastic-2.0 No Details →
25.11.0 26 Nov 2025 H1 M1 L1 U4 Elastic-2.0 No Details →
25.11.0rc2 21 Nov 2025 H1 M1 L1 U4 Elastic-2.0 No Details →
25.11.0rc1 11 Nov 2025 H1 M1 L1 U4 Elastic-2.0 No Details →
25.10.1 27 Oct 2025 H1 M1 L1 U4 Elastic-2.0 No Details →
25.10.0 23 Oct 2025 H1 M1 L1 U4 Elastic-2.0 No Details →
25.10.0rc1 17 Oct 2025 H1 M1 L1 U4 Elastic-2.0 No Details →
25.9.3rc1 24 Sep 2025 H1 M1 L1 U4 Elastic-2.0 No Details →
25.9.2.0a1 09 Sep 2025 H1 M1 L1 U9 Elastic-2.0 No Details →
25.9.1.2 05 Sep 2025 H1 M1 L1 U9 Elastic-2.0 No Details →
25.9.1.1 04 Sep 2025 H1 M1 L1 U9 Elastic-2.0 No Details →
25.9.1.0 04 Sep 2025 H2 M1 L1 U10 Elastic-2.0 No Details →
25.8.3.0 28 Aug 2025 H2 M1 L1 U10 Elastic-2.0 No Details →
25.8.2.0 19 Aug 2025 H2 M1 L1 U10 Elastic-2.0 No Details →
25.7.4.0 29 Jul 2025 H2 M1 L1 U10 Elastic-2.0 No Details →
25.7.3.0 15 Jul 2025 H2 M1 L1 U10 Elastic-2.0 No Details →
25.7.2.0 09 Jul 2025 H2 M1 L1 U10 Elastic-2.0 No Details →
25.7.1.0 02 Jul 2025 H2 M1 L1 U10 Elastic-2.0 No Details →
25.6.4.0 24 Jun 2025 H2 M1 L1 U10 Elastic-2.0 No Details →
25.6.3.1 19 Jun 2025 H2 M1 L1 U10 Elastic-2.0 No Details →
25.6.3.0 17 Jun 2025 H2 M1 L1 U10 Elastic-2.0 No Details →
25.6.2.0 10 Jun 2025 H2 M1 L1 U10 Elastic-2.0 No Details →
25.5.4.2 30 May 2025 H2 M1 L1 U10 Elastic-2.0 No Details →
25.5.4.1 29 May 2025 H2 M1 L1 U10 Elastic-2.0 No Details →
25.5.4.0 27 May 2025 H2 M1 L1 U10 Elastic-2.0 No Details →
25.5.3.0 17 May 2025 H2 M1 L1 U10 Elastic-2.0 No Details →
25.4.5.0 29 Apr 2025 H2 M1 L1 U10 Elastic-2.0 No Details →
25.4.4.0 22 Apr 2025 H2 M1 L1 U10 Elastic-2.0 No Details →
25.4.3.2 16 Apr 2025 H2 M1 L1 U10 Elastic-2.0 No Details →
25.4.3.1 15 Apr 2025 H2 M1 L1 U10 Elastic-2.0 No Details →
25.4.3.0 15 Apr 2025 H2 M1 L1 U10 Elastic-2.0 No Details →
25.4.2.1 10 Apr 2025 H2 M1 L1 U10 Elastic-2.0 No Details →
25.4.2.0 08 Apr 2025 H2 M1 L1 U10 Elastic-2.0 No Details →
25.4.1.0 01 Apr 2025 H2 M1 L1 U10 Elastic-2.0 No Details →
25.3.4.2 27 Mar 2025 H2 M1 L1 U10 Elastic-2.0 No Details →
25.3.4.1 26 Mar 2025 H2 M1 L1 U10 Elastic-2.0 No Details →
25.3.4.0 24 Mar 2025 H2 M1 L1 U10 non-standard No Details →
25.3.3.0 18 Mar 2025 H2 M1 L1 U10 non-standard No Details →
25.3.2.0 11 Mar 2025 H2 M1 L1 U10 non-standard No Details →
25.3.1.0 04 Mar 2025 H2 M1 L1 U10 non-standard No Details →
25.2.4.0 25 Feb 2025 H2 M1 L1 U10 non-standard No Details →
25.2.3.0 18 Feb 2025 H2 M1 L1 U10 non-standard No Details →
25.2.2.2 14 Feb 2025 H2 M1 L1 U10 non-standard No Details →
25.2.2.0 11 Feb 2025 H2 M1 L1 U10 non-standard No Details →
25.2.1.2 04 Feb 2025 H2 M1 L1 U10 non-standard No Details →
25.2.1.0 04 Feb 2025 H2 M1 L1 U10 non-standard No Details →
25.1.5.3 30 Jan 2025 H2 M1 L1 U10 non-standard No Details →
25.1.5.2 30 Jan 2025 H2 M1 L1 U10 non-standard No Details →
25.1.5.1 30 Jan 2025 H2 M1 L1 U10 non-standard No Details →
25.1.5.0 28 Jan 2025 H2 M1 L1 U10 non-standard No Details →
25.1.4.0 21 Jan 2025 H2 M1 L1 U10 non-standard No Details →
25.1.3.0 14 Jan 2025 H2 M1 L1 U10 non-standard No Details →
25.1.2.1 10 Jan 2025 H2 M1 L1 U10 non-standard No Details →
25.1.2.0 07 Jan 2025 H2 M1 L1 U10 non-standard No Details →
24.12.4.0 24 Dec 2024 H2 M1 L1 U10 non-standard No Details →
24.12.2.2 19 Dec 2024 H2 M1 L1 U10 non-standard No Details →
24.12.3.0 17 Dec 2024 H2 M1 L1 U10 non-standard No Details →
24.12.2.1 11 Dec 2024 H2 M1 L1 U10 non-standard No Details →
24.12.2.0 10 Dec 2024 H2 M1 L1 U10 non-standard No Details →
24.12.1.0 03 Dec 2024 H2 M1 L1 U10 non-standard No Details →
24.11.4.2 29 Nov 2024 H2 M1 L1 U10 non-standard No Details →
24.11.4.1 28 Nov 2024 H2 M1 L1 U10 non-standard No Details →
24.11.4.0 26 Nov 2024 H2 M1 L1 U10 non-standard No Details →
24.11.3.0 19 Nov 2024 H2 M1 L1 U10 non-standard No Details →
24.11.2.0 12 Nov 2024 H2 M1 L1 U10 non-standard No Details →
24.11.1.1 08 Nov 2024 H2 M1 L1 U10 non-standard No Details →
24.11.1.0 05 Nov 2024 H2 M1 L1 U10 non-standard No Details →
24.10.5.0 29 Oct 2024 H2 M1 L1 U10 non-standard No Details →
24.10.4.2 24 Oct 2024 H2 M1 L1 U10 non-standard No Details →
24.10.4.1 24 Oct 2024 H2 M1 L1 U10 non-standard No Details →
24.10.4.0 22 Oct 2024 H2 M1 L1 U10 non-standard No Details →
24.10.3.0 15 Oct 2024 H2 M1 L1 U10 non-standard No Details →
24.10.2.0 08 Oct 2024 H2 M1 L1 U10 non-standard No Details →
24.10.1.0 01 Oct 2024 H2 M1 L1 U10 non-standard No Details →
24.9.4.1 27 Sep 2024 H2 M1 L1 U10 non-standard No Details →
24.9.4.0 25 Sep 2024 H2 M1 L1 U10 non-standard No Details →
24.9.3.2 18 Sep 2024 H2 M1 L1 U10 non-standard No Details →
24.9.3.1 18 Sep 2024 H2 M1 L1 U10 non-standard No Details →
24.9.3.0 17 Sep 2024 H2 M1 L1 U10 non-standard No Details →
24.9.2.1 10 Sep 2024 H6 M2 L1 U11 non-standard No Details →
24.9.2.0 10 Sep 2024 H6 M2 L1 U11 non-standard No Details →
24.9.1.0 03 Sep 2024 H6 M2 L1 U11 non-standard No Details →
24.8.4.0 27 Aug 2024 H6 M2 L1 U11 non-standard No Details →
24.8.3.0 20 Aug 2024 H6 M2 L1 U11 non-standard No Details →
24.8.2.0 13 Aug 2024 H6 M2 L1 U11 — No Details →
24.8.1.1 07 Aug 2024 H6 M2 L1 U11 — No Details →
24.8.1.0 06 Aug 2024 H6 M2 L1 U11 — No Details →
24.7.5.0 30 Jul 2024 H6 M2 L1 U11 — No Details →
24.7.4.1 24 Jul 2024 H6 M2 L1 U11 — No Details →
24.7.4.0 23 Jul 2024 H12 M2 L1 U17 — No Details →
24.7.3.0 16 Jul 2024 H12 M2 L1 U17 — No Details →
24.7.2.0 08 Jul 2024 H12 M2 L1 U17 — No Details →
24.7.1.0 02 Jul 2024 H12 M2 L1 U17 — No Details →
24.6.4.1 25 Jun 2024 H12 M2 L1 U17 — No Details →
24.6.3.1 19 Jun 2024 H12 M2 L1 U17 — No Details →
24.6.3.0 18 Jun 2024 H12 M2 L1 U17 — No Details →
24.6.2.2 12 Jun 2024 H12 M2 L1 U17 — No Details →
24.6.2.0 11 Jun 2024 H12 M2 L1 U17 — No Details →
24.6.1.1 07 Jun 2024 H12 M2 L1 U17 — No Details →
24.6.1.0 04 Jun 2024 H12 M2 L1 U17 — No Details →
24.5.4.0 22 May 2024 H12 M2 L1 U17 — No Details →
24.4.3.0 15 Apr 2024 H12 M2 L1 U17 — No Details →
24.4.2.1 11 Apr 2024 H12 M2 L1 U17 — No Details →
24.4.2.0 10 Apr 2024 H12 M2 L1 U17 — No Details →

The newest 120 of 579 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 12
  • 2024 24
  • 2026 10

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

03 Vulnerabilities

Recorded vulnerabilities for mindsdb

The 5 most severe of 46 vulnerabilities recorded for this package

Search all 46 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-24759: MindsDB Vulnerable to Bypass of SSRF Protection with DNS Rebinding 9.3 high 23.12.4.2 05 Sep 2024
CVE-2025-68472: MindsDB Unauthenticated Path Traversal Vulnerability in File Upload API 9.1 critical 25.11.1 12 Jan 2026
CVE-2024-24759: Server-Side Request Forgery Protection Bypass in MindsDB 9.1 critical 5f7496481bd3db1d06a2d2e62c0dce960a1fe12b 05 Sep 2024
Arbitrary Write Vulnerability in mindsdb 9.1 high 23.11.4.1 15 Dec 2023
CVE-2023-38699: MindsDB SSL Certificate Verification Bypass 9.1 critical 23.7.4.0 01 Aug 2023

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 mindsdb

Is mindsdb safe to use?

Vulert records 46 vulnerabilities for mindsdb in PyPI: 1 critical, 15 high, 6 medium and 1 low, plus 23 not yet rated. 15 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is mindsdb's Vulert package health score?

Vulert scores mindsdb 50/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of mindsdb affected?

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

Which version of mindsdb should I use?

26.1.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 mindsdb have?

46 vulnerabilities are recorded for mindsdb in the PyPI ecosystem: 1 critical, 15 high, 6 medium and 1 low, plus 23 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 mindsdb vulnerabilities disclosed?

10 vulnerabilities were recorded for mindsdb in the last 12 months, and the oldest entry in this database dates to 30 Mar 2023. 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 mindsdb 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 mindsdb for upcoming vulnerabilities?

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