VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

pyodbc: vulnerability history, versions and safety

pyodbc is a package in the PyPI ecosystem. Vulert records 1 vulnerability for it across 63 releases, first recorded in May 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
i
1 with no fix published

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

See the unfixed vulnerabilities →
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 pyodbc vulnerabilities

Vulert verdict on pyodbc 5.3.0 i

Updated on 23 Oct 2026

Careful: 5.3.0 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor 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 5.3.0 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 27 May 2025 i
  • Highest CVSS n/a i
  • With no published fix 1 i
  • Depended on by 893 packages i
  • Stars 3,089 i
  • OpenSSF scorecard 5/10 i
  • Last release 12 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 pyodbc, 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
5.3.0 17 Oct 2025 M1 MIT No Details →
5.2.0 16 Oct 2024 M1 non-standard No Details →
5.1.0 05 Feb 2024 M1 MIT No Details →
5.0.1 13 Oct 2023 M1 MIT No Details →
5.0.0 10 Oct 2023 M1 MIT No Details →
5.0.0b3 29 Aug 2023 M1 MIT No Details →
5.0.0b2 28 Aug 2023 M1 MIT No Details →
5.0.0b1 27 Aug 2023 M1 MIT No Details →
5.0.0a2 26 Aug 2023 M1 MIT No Details →
4.0.39 14 Apr 2023 M1 MIT No Details →
4.0.38 11 Apr 2023 M1 MIT No Details →
4.0.35 16 Nov 2022 M1 MIT No Details →
4.0.34 14 Jul 2022 M1 MIT No Details →
4.0.32 19 Aug 2021 M1 MIT No Details →
4.0.31 04 Jul 2021 M1 MIT No Details →
4.0.30 20 Feb 2020 M1 MIT No Details →
4.0.30b1 10 Feb 2020 M1 MIT No Details →
4.0.28 21 Dec 2019 M1 MIT No Details →
4.0.27 31 Jul 2019 M1 MIT No Details →
4.0.26 23 Feb 2019 M1 MIT No Details →
4.0.25 14 Dec 2018 M1 MIT No Details →
4.0.24 15 Aug 2018 M1 MIT No Details →
4.0.23 30 Mar 2018 M1 MIT No Details →
4.0.22 19 Jan 2018 M1 MIT No Details →
4.0.21 31 Oct 2017 M1 MIT No Details →
4.0.20 31 Oct 2017 M1 MIT No Details →
4.0.19 23 Oct 2017 M1 MIT No Details →
4.0.18 20 Oct 2017 M1 MIT No Details →
4.0.17 21 Jun 2017 M1 MIT No Details →
4.0.16 30 Mar 2017 M1 MIT No Details →
4.0.15 15 Mar 2017 M1 MIT No Details →
4.0.14 04 Mar 2017 M1 MIT No Details →
4.0.13 25 Feb 2017 M1 MIT No Details →
4.0.12 25 Feb 2017 M1 MIT No Details →
4.0.11 19 Feb 2017 M1 MIT No Details →
4.0.10 19 Feb 2017 M1 MIT No Details →
4.0.9 19 Feb 2017 M1 MIT No Details →
4.0.8 17 Feb 2017 M1 MIT No Details →
4.0.7 16 Feb 2017 M1 MIT No Details →
4.0.6 13 Feb 2017 M1 MIT No Details →
4.0.5 11 Feb 2017 M1 MIT No Details →
4.0.3 20 Jan 2017 M1 MIT No Details →
4.0.2 19 Jan 2017 M1 MIT No Details →
4.0.1 13 Jan 2017 M1 MIT No Details →
3.1.1 29 Nov 2016 M1 MIT No Details →
3.0.7 24 Sep 2015 M1 MIT No Details →
3.0.6 24 Sep 2015 M1 MIT No Details →
3.0.3 24 Sep 2015 M1 MIT No Details →
2.1.9 24 Sep 2015 M1 MIT No Details →
2.1.8 24 Sep 2015 M1 MIT No Details →
2.1.7 24 Sep 2015 M1 MIT No Details →
2.1.6 24 Sep 2015 M1 MIT No Details →
2.1.5 24 Sep 2015 M1 MIT No Details →
2.1.4 24 Sep 2015 M1 MIT No Details →
2.1.3 24 Sep 2015 M1 MIT No Details →
2.1.2 24 Sep 2015 M1 MIT No Details →
2.1.11 24 Sep 2015 M1 MIT No Details →
2.1.10 24 Sep 2015 M1 MIT No Details →
2.1.1 24 Sep 2015 M1 MIT No Details →
3.0.10 29 Apr 2015 M1 MIT No Details →
3.0.9 28 Apr 2015 M1 MIT No Details →
3.0.8 25 Apr 2015 M1 MIT No Details →
4.0.0 — M1 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for pyodbc

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap Buffer Overflow Vulnerability in pyodbc Package N/A medium No fix published 27 May 2025

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 pyodbc

Is pyodbc safe to use?

Vulert records 1 vulnerabilities for pyodbc in PyPI: 0 critical, 0 high, 1 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is pyodbc's Vulert package health score?

Vulert scores pyodbc 60/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 pyodbc affected?

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

Which version of pyodbc should I use?

5.3.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 pyodbc have?

1 vulnerability is recorded for pyodbc in the PyPI ecosystem: 0 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 pyodbc vulnerabilities disclosed?

0 vulnerabilities were recorded for pyodbc in the last 12 months, and the oldest entry in this database dates to 27 May 2025. 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 pyodbc 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 pyodbc for upcoming vulnerabilities?

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