VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

mssql-django: vulnerability history, versions and safety

mssql-django is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 11 releases, from Mar 2024 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
2 vulnerabilities recorded H1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mssql-django vulnerabilities

Vulert verdict on mssql-django 2.0.0 i

Updated on 23 Oct 2026

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

Package health score 78/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

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

  • Current release 2.0.0 — unaffected i
  • Vulnerabilities on record 2 over 2 years · 1 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Depended on by 2 packages i
  • Last release 1 month 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 mssql-django, 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
2.0.0 18 Sep 2026 none non-standard — Details →
1.8.0 07 Aug 2026 none non-standard — Details →
1.7.4 24 Jul 2026 none non-standard — Details →
1.7.3 19 Jun 2026 none non-standard — Details →
1.7.2 22 May 2026 none non-standard — Details →
1.7.1 24 Apr 2026 none non-standard — Details →
1.7.0 06 Mar 2026 none non-standard — Details →
1.6.0 08 Aug 2025 none non-standard — Details →
1.5.0 26 Apr 2024 none non-standard — Details →
1.4.2 14 Mar 2024 none non-standard — Details →
1.4.1 12 Mar 2024 none non-standard — Details →
1.4.0 15 Jan 2024 H1 U1 non-standard Yes Details →
1.3.0 01 Jun 2023 H1 U1 non-standard Yes Details →
1.2.0 08 Dec 2022 H1 U1 non-standard Yes Details →
1.1.3 27 Apr 2022 H1 U1 non-standard Yes Details →
1.1.2 31 Jan 2022 H1 U1 non-standard Yes Details →
1.1.1 09 Dec 2021 H1 U1 non-standard Yes Details →
1.1.0 30 Nov 2021 H1 U1 non-standard Yes Details →
1.0.0 29 Jul 2021 H1 U1 non-standard Yes Details →
1.0.0rc1 30 Jun 2021 H1 U1 non-standard Yes Details →
1.0.0b1 19 Mar 2021 H1 U1 non-standard Yes Details →
1.0.0a5 18 Feb 2021 H1 U1 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for mssql-django

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-26164: Remote Code Execution Vulnerability in Microsoft Django Backend for SQL Server 8.8 high 1.4.1 12 Mar 2024
CVE-2024-26164: Remote Code Execution Vulnerability in mssql-django Package 8.8 high 1.4.1 07 Jul 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 mssql-django

Is mssql-django safe to use?

Vulert records 2 vulnerabilities for mssql-django 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 mssql-django's Vulert package health score?

Vulert scores mssql-django 78/100, which reads as in good shape. 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 mssql-django affected?

No. 2.0.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 mssql-django should I use?

2.0.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 mssql-django have?

2 vulnerabilities are recorded for mssql-django 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 mssql-django vulnerabilities disclosed?

1 vulnerability was recorded for mssql-django in the last 12 months, and the oldest entry in this database dates to 12 Mar 2024. 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 mssql-django 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 mssql-django for upcoming vulnerabilities?

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