VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

sqlalchemy: vulnerability history, versions and safety

sqlalchemy is a package in the PyPI ecosystem. Vulert records 8 vulnerabilities for it across 0 release, from Jun 2012 to May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
8 vulnerabilities recorded C3 U5
i
0 with no fix published

Every vulnerability has a patched version to move to.

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 sqlalchemy vulnerabilities

Vulert verdict on sqlalchemy 2.1.6 i

Updated on 23 Oct 2026

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

Package health score 83/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 2.1.6 — unaffected i
  • Vulnerabilities on record 8 over 9 years · 0 in the last year i
  • Latest disclosure 14 May 2022 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 23,101 packages i
  • Stars 12,253 i
  • OpenSSF scorecard 4/10 i
  • Last release this month 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 sqlalchemy, 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.1.6 21 Oct 2026 none MIT — Details →
2.1.5 16 Oct 2026 none MIT — Details →
2.0.55 16 Oct 2026 none MIT — Details →
2.1.4 07 Oct 2026 none MIT — Details →
2.1.3 03 Oct 2026 none MIT — Details →
2.1.2 02 Oct 2026 none MIT — Details →
2.1.1 25 Sep 2026 none MIT — Details →
2.1.0 24 Sep 2026 none MIT — Details →
2.0.54 15 Sep 2026 none MIT — Details →
2.0.53 14 Sep 2026 none MIT — Details →
2.1.0rc2 08 Sep 2026 none MIT — Details →
2.1.0rc1 01 Sep 2026 none MIT — Details →
2.0.52 11 Aug 2026 none MIT — Details →
2.1.0b3 27 Jun 2026 none MIT — Details →
2.0.51 15 Jun 2026 none MIT — Details →
2.0.50 24 May 2026 none MIT — Details →
2.1.0b2 16 Apr 2026 none MIT — Details →
2.0.49 03 Apr 2026 none MIT — Details →
2.0.48 02 Mar 2026 none MIT — Details →
2.0.47 24 Feb 2026 none MIT — Details →
2.1.0b1 21 Jan 2026 none MIT — Details →
2.0.46 21 Jan 2026 none MIT — Details →
2.0.45 09 Dec 2025 none MIT — Details →
2.0.44 10 Oct 2025 none MIT — Details →
2.0.43 11 Aug 2025 none MIT — Details →
2.0.42 29 Jul 2025 none MIT — Details →
2.0.41 14 May 2025 none MIT — Details →
2.0.40 27 Mar 2025 none MIT — Details →
2.0.39 11 Mar 2025 none MIT — Details →
2.0.38 06 Feb 2025 none MIT — Details →
2.0.37 10 Jan 2025 none MIT — Details →
2.0.36 15 Oct 2024 none MIT — Details →
2.0.35 16 Sep 2024 none MIT — Details →
1.4.54 05 Sep 2024 none MIT — Details →
2.0.34 04 Sep 2024 none MIT — Details →
2.0.33 03 Sep 2024 none MIT — Details →
2.0.32 05 Aug 2024 none MIT — Details →
1.4.53 29 Jul 2024 none MIT — Details →
2.0.31 18 Jun 2024 none MIT — Details →
2.0.30 05 May 2024 none MIT — Details →
2.0.29 23 Mar 2024 none MIT — Details →
2.0.28 04 Mar 2024 none MIT — Details →
1.4.52 04 Mar 2024 none MIT — Details →
2.0.27 13 Feb 2024 none MIT — Details →
2.0.26 11 Feb 2024 none MIT — Details →
1.4.51 03 Jan 2024 none MIT — Details →
2.0.25 03 Jan 2024 none MIT — Details →
2.0.24 28 Dec 2023 none MIT — Details →
2.0.23 02 Nov 2023 none MIT — Details →
1.4.50 29 Oct 2023 none MIT — Details →
2.0.22 12 Oct 2023 none MIT — Details →
1.4.49 06 Oct 2023 none MIT — Details →
2.0.21 18 Sep 2023 none MIT — Details →
2.0.20 15 Aug 2023 none MIT — Details →
2.0.19 15 Jul 2023 none MIT — Details →
2.0.18 05 Jul 2023 none MIT — Details →
2.0.17 23 Jun 2023 none MIT — Details →
2.0.16 10 Jun 2023 none MIT — Details →
2.0.15 20 May 2023 none MIT — Details →
2.0.14 18 May 2023 none MIT — Details →
2.0.13 10 May 2023 none MIT — Details →
1.4.48 30 Apr 2023 none MIT — Details →
2.0.12 30 Apr 2023 none MIT — Details →
2.0.11 27 Apr 2023 none MIT — Details →
2.0.10 21 Apr 2023 none MIT — Details →
2.0.9 06 Apr 2023 none MIT — Details →
2.0.8 31 Mar 2023 none MIT — Details →
1.4.47 18 Mar 2023 none MIT — Details →
2.0.7 18 Mar 2023 none MIT — Details →
2.0.6 13 Mar 2023 none MIT — Details →
2.0.5.post1 06 Mar 2023 none MIT — Details →
2.0.5 06 Mar 2023 none MIT — Details →
2.0.4 17 Feb 2023 none MIT — Details →
2.0.3 10 Feb 2023 none MIT — Details →
2.0.2 07 Feb 2023 none MIT — Details →
2.0.1 01 Feb 2023 none MIT — Details →
2.0.0 26 Jan 2023 none MIT — Details →
2.0.0rc3 19 Jan 2023 none MIT — Details →
2.0.0rc2 09 Jan 2023 none MIT — Details →
1.4.46 03 Jan 2023 none MIT — Details →
2.0.0rc1 29 Dec 2022 none MIT — Details →
1.4.45 10 Dec 2022 none MIT — Details →
2.0.0b4 06 Dec 2022 none MIT — Details →
1.4.44 12 Nov 2022 none MIT — Details →
2.0.0b3 04 Nov 2022 none MIT — Details →
1.4.43 04 Nov 2022 none MIT — Details →
2.0.0b2 20 Oct 2022 none MIT — Details →
1.4.42 16 Oct 2022 none MIT — Details →
2.0.0b1 13 Oct 2022 none MIT — Details →
1.4.41 07 Sep 2022 none MIT — Details →
1.4.40 08 Aug 2022 none MIT — Details →
1.4.39 24 Jun 2022 none MIT — Details →
1.4.38 23 Jun 2022 none MIT — Details →
1.4.37 31 May 2022 none MIT — Details →
1.4.36 26 Apr 2022 none MIT — Details →
1.4.35 06 Apr 2022 none MIT — Details →
1.4.34 31 Mar 2022 none MIT — Details →
1.4.33 31 Mar 2022 none MIT — Details →
1.4.32 06 Mar 2022 none MIT — Details →
1.4.31 21 Jan 2022 none MIT — Details →
1.4.30 19 Jan 2022 none — — Details →
1.4.29 23 Dec 2021 none — — Details →
1.4.28 09 Dec 2021 none — — Details →
1.4.27 11 Nov 2021 none — — Details →
1.4.26 20 Oct 2021 none — — Details →
1.4.25 23 Sep 2021 none — — Details →
1.4.24 22 Sep 2021 none — — Details →
1.4.23 18 Aug 2021 none — — Details →
1.4.22 22 Jul 2021 none — — Details →
1.4.21 14 Jul 2021 none — — Details →
1.4.20 28 Jun 2021 none — — Details →
1.4.19 23 Jun 2021 none — — Details →
1.4.18 10 Jun 2021 none — — Details →
1.4.17 29 May 2021 none — — Details →
1.4.16 28 May 2021 none — — Details →
1.4.15 11 May 2021 none — — Details →
1.4.14 06 May 2021 none — — Details →
1.4.13 03 May 2021 none — — Details →
1.4.12 29 Apr 2021 none — — Details →
1.4.11 22 Apr 2021 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2012 1
  • 2019 6
  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for sqlalchemy

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-7164: SQLAlchemy SQL Injection Vulnerability 9.8 critical 1.3.0b3 16 Apr 2019
CVE-2012-0805: SQLAlchemy SQL Injection Vulnerability 9.8 critical 0.7.0b4 14 May 2022
CVE-2019-7548: SQL Injection in SQLAlchemy 7.8 critical 1.2.19 16 Apr 2019
CVE-2012-0805: SQL Injection Vulnerabilities in SQLAlchemy N/A unrated 0.7.0 05 Jun 2012
CVE-2019-7164: SQL Injection in SQLAlchemy N/A unrated 1.2.18 20 Feb 2019

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 sqlalchemy

Is sqlalchemy safe to use?

Vulert records 8 vulnerabilities for sqlalchemy in PyPI: 3 critical, 0 high, 0 medium and 0 low, plus 5 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 sqlalchemy's Vulert package health score?

Vulert scores sqlalchemy 83/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 sqlalchemy affected?

No. 2.1.6, 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.

How many vulnerabilities does sqlalchemy have?

8 vulnerabilities are recorded for sqlalchemy in the PyPI ecosystem: 3 critical, 0 high, 0 medium and 0 low, plus 5 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 sqlalchemy vulnerabilities disclosed?

0 vulnerabilities were recorded for sqlalchemy in the last 12 months, and the oldest entry in this database dates to 05 Jun 2012. 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 sqlalchemy 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 sqlalchemy for upcoming vulnerabilities?

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