VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

pymysql: vulnerability history, versions and safety

pymysql is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 43 releases, from May 2024 to Jun 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 C1 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 29 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all pymysql vulnerabilities

Vulert verdict on pymysql 1.2.3 i

Updated on 23 Oct 2026

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

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

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

  • Current release 1.2.3 — unaffected i
  • Vulnerabilities on record 2 over 2 years · 1 in the last year i
  • Latest disclosure 29 Jun 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 2,801 packages i
  • Stars 7,856 i
  • OpenSSF scorecard 6/10 i
  • Last release 1 month 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 pymysql, 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
1.2.3 17 Sep 2026 none MIT — Details →
1.2.2 17 Sep 2026 none MIT — Details →
1.2.1 17 Sep 2026 none MIT — Details →
1.2.0 19 May 2026 none MIT — Details →
1.1.3 01 May 2026 none MIT — Details →
1.1.2 24 Aug 2025 none MIT — Details →
1.1.1 21 May 2024 none MIT — Details →
1.1.0 26 Jun 2023 C1 U1 MIT Yes Details →
1.1.0rc2 15 Jun 2023 C1 U1 MIT Yes Details →
1.1.0rc1 25 May 2023 C1 U1 MIT Yes Details →
1.0.3 28 Mar 2023 C1 U1 MIT Yes Details →
1.0.3rc1 24 Mar 2023 C1 U1 MIT Yes Details →
1.0.2 09 Jan 2021 C1 U1 non-standard Yes Details →
1.0.1 08 Jan 2021 C1 U1 non-standard Yes Details →
1.0.0 07 Jan 2021 C1 U1 non-standard Yes Details →
0.10.1 10 Sep 2020 C1 U1 non-standard Yes Details →
0.10.0 18 Jul 2020 C1 U1 non-standard Yes Details →
0.9.3 18 Dec 2018 C1 U1 non-standard Yes Details →
0.9.2 04 Jul 2018 C1 U1 non-standard Yes Details →
0.9.1 02 Jul 2018 C1 U1 MIT Yes Details →
0.9.0 27 Jun 2018 C1 U1 MIT Yes Details →
0.8.1 07 May 2018 C1 U1 MIT Yes Details →
0.8.0 20 Dec 2017 C1 U1 MIT Yes Details →
0.7.11 05 Apr 2017 C1 U1 MIT Yes Details →
0.7.10 14 Feb 2017 C1 U1 MIT Yes Details →
0.7.9 03 Sep 2016 C1 U1 MIT Yes Details →
0.7.8 01 Sep 2016 C1 U1 MIT Yes Details →
0.7.7 29 Aug 2016 C1 U1 MIT Yes Details →
0.7.6 29 Jul 2016 C1 U1 MIT Yes Details →
0.7.5 28 Jun 2016 C1 U1 MIT Yes Details →
0.7.4 26 May 2016 C1 U1 MIT Yes Details →
0.7.3 19 May 2016 C1 U1 MIT Yes Details →
0.7.2 24 Feb 2016 C1 U1 MIT Yes Details →
0.7.1 14 Jan 2016 C1 U1 MIT Yes Details →
0.7.0 10 Jan 2016 C1 U1 MIT Yes Details →
0.6.7 30 Sep 2015 C1 U1 MIT Yes Details →
0.6.6 28 Feb 2015 C1 U1 MIT Yes Details →
0.6.4 25 Feb 2015 C1 U1 MIT Yes Details →
0.6.4.dev1 25 Feb 2015 C1 U1 MIT Yes Details →
0.6.3 02 Dec 2014 C1 U1 MIT Yes Details →
0.6.2 21 Apr 2014 C1 U1 MIT Yes Details →
0.6.1 21 Nov 2013 C1 U1 MIT Yes Details →
0.6.0 04 Oct 2013 C1 U1 MIT Yes Details →
0.5.0 08 Nov 2011 C1 U1 MIT Yes Details →
0.4.0 27 Dec 2010 C1 U1 MIT Yes Details →
0.3.0 14 Dec 2010 C1 U1 — Yes Details →
0.2-py2.5 — C1 U1 — Yes Details →
0.2-py2.6 — C1 U1 — Yes Details →
0.3-py2.6 — C1 U1 — Yes Details →
0.3_1-py2.6 — C1 U1 — Yes Details →

All 50 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 pymysql

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-36039: PyMySQL SQL Injection vulnerability 9.8 critical 1.1.1 21 May 2024
CVE-2024-36039: PyMySQL SQL Injection Vulnerability 9.8 critical 1.1.1 29 Jun 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 pymysql

Is pymysql safe to use?

Vulert records 2 vulnerabilities for pymysql in PyPI: 1 critical, 0 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 pymysql's Vulert package health score?

Vulert scores pymysql 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 pymysql affected?

No. 1.2.3, 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 pymysql should I use?

1.2.3 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 pymysql have?

2 vulnerabilities are recorded for pymysql in the PyPI ecosystem: 1 critical, 0 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 pymysql vulnerabilities disclosed?

1 vulnerability was recorded for pymysql in the last 12 months, and the oldest entry in this database dates to 21 May 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 pymysql 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 pymysql for upcoming vulnerabilities?

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