VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

mysql-connector-python: vulnerability history, versions and safety

mysql-connector-python is a package in the PyPI ecosystem. Vulert records 6 vulnerabilities for it across 25 releases, from May 2022 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
6 vulnerabilities recorded H2 L1 U3
i
2 with no fix published

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

See the unfixed vulnerabilities →
i
3 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 mysql-connector-python vulnerabilities

Vulert verdict on mysql-connector-python 26.10.0 i

Updated on 23 Oct 2026

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

Package health score 60/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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.10.0 — affected i
  • Vulnerabilities on record 6 over 4 years · 3 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 8.1 i
  • With no published fix 2 i
  • Stars 953 i
  • OpenSSF scorecard 2/10 i
  • Last release this month 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 mysql-connector-python, 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.10.0 22 Oct 2026 L1 U1 non-standard No Details →
26.7.0 29 Jul 2026 L1 U1 non-standard No Details →
9.7.0 30 Apr 2026 L1 U1 non-standard No Details →
9.6.0 10 Feb 2026 L1 U1 non-standard No Details →
9.5.0 22 Oct 2025 L1 U1 non-standard No Details →
9.4.0 22 Jul 2025 L1 U1 non-standard No Details →
9.3.0 15 Apr 2025 L1 U1 non-standard No Details →
9.1.0 15 Oct 2024 L1 U1 non-standard No Details →
9.0.0 01 Jul 2024 H1 U1 non-standard Yes Details →
8.4.0 30 Apr 2024 H1 U1 non-standard Yes Details →
8.3.0 16 Jan 2024 H1 U1 non-standard Yes Details →
8.2.0 25 Oct 2023 H1 U1 non-standard Yes Details →
8.1.0 18 Jul 2023 H1 U1 non-standard Yes Details →
8.0.33 18 Apr 2023 H1 U1 non-standard Yes Details →
8.0.32 17 Jan 2023 H1 U1 non-standard Yes Details →
8.0.31 11 Oct 2022 H1 U1 non-standard Yes Details →
8.0.30 26 Jul 2022 H1 U1 non-standard Yes Details →
8.0.29 26 Apr 2022 H1 U1 non-standard Yes Details →
8.0.28 18 Jan 2022 H1 U1 non-standard Yes Details →
8.0.27 19 Oct 2021 H1 U1 non-standard Yes Details →
8.0.26 20 Jul 2021 H1 U1 non-standard Yes Details →
8.0.25 11 May 2021 H1 U1 non-standard Yes Details →
8.0.23 18 Jan 2021 H1 U1 non-standard Yes Details →
8.0.5 20 Nov 2017 H2 U2 non-standard Yes Details →
9.2.0 — L1 U1 non-standard No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2
  • 2024 1
  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for mysql-connector-python

The 5 most severe of 6 vulnerabilities recorded for this package

Search all 6 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-2435: Improper Access Control in MySQL Connector Python 8.1 high 8.0.19 13 May 2022
CVE-2019-2435: MySQL Connector Python Improper Access Control Vulnerability 8.1 high 8.0.19 02 Jul 2026
Critical Takeover Vulnerability in MySQL Connector/Python (CVSS 7.5) 7.5 high 9.1.0 15 Oct 2024
CVE-2024-21272: mysql-connector-python Connector Takeover Vulnerability 7.5 high 9.1.0 07 Jul 2026
CVE-2017-3590: MySQL Connectors Privilege Escalation 3.3 low No fix published 13 May 2022

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 mysql-connector-python

Is mysql-connector-python safe to use?

Vulert records 6 vulnerabilities for mysql-connector-python in PyPI: 0 critical, 2 high, 0 medium and 1 low, plus 3 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is mysql-connector-python's Vulert package health score?

Vulert scores mysql-connector-python 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 mysql-connector-python affected?

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

How many vulnerabilities does mysql-connector-python have?

6 vulnerabilities are recorded for mysql-connector-python in the PyPI ecosystem: 0 critical, 2 high, 0 medium and 1 low, plus 3 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 mysql-connector-python vulnerabilities disclosed?

3 vulnerabilities were recorded for mysql-connector-python in the last 12 months, and the oldest entry in this database dates to 13 May 2022. 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 mysql-connector-python 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 mysql-connector-python for upcoming vulnerabilities?

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