VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

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

mysql:mysql-connector-java is a package in the Maven ecosystem. Vulert records 8 vulnerabilities for it across 86 releases, from Jul 2020 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 H2 M5 L1
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 mysql:mysql-connector-java vulnerabilities

Vulert verdict on mysql:mysql-connector-java 8.0.33 i

Updated on 22 Oct 2026

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

Package health score 69/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Moderate

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

  • Current release 8.0.33 — unaffected i
  • Vulnerabilities on record 8 over 1 year · 0 in the last year i
  • Latest disclosure 24 May 2022 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Depended on by 768 packages i
  • Stars 1,015 i
  • OpenSSF scorecard 3/10 i
  • Last release 43 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by Maven Central, 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:mysql-connector-java, 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
8.0.33 07 Mar 2023 none — — Details →
8.0.32 07 Dec 2022 none — — Details →
8.0.31 03 Sep 2022 none — — Details →
8.0.30 01 Jul 2022 none non-standard — Details →
8.0.29 08 Mar 2022 none non-standard — Details →
8.0.28 16 Dec 2021 none non-standard — Details →
8.0.27 28 Sep 2021 M1 non-standard Yes Details →
8.0.26 08 Jun 2021 M2 non-standard Yes Details →
8.0.25 27 Apr 2021 M2 non-standard Yes Details →
8.0.24 02 Mar 2021 M2 non-standard Yes Details →
8.0.23 01 Dec 2020 M2 non-standard Yes Details →
8.0.22 10 Sep 2020 M2 non-standard Yes Details →
8.0.21 16 Jun 2020 M2 non-standard Yes Details →
5.1.49 20 Apr 2020 H1 M2 non-standard Yes Details →
8.0.20 09 Mar 2020 M2 non-standard Yes Details →
8.0.19 04 Dec 2019 M2 non-standard Yes Details →
8.0.18 08 Sep 2019 M2 non-standard Yes Details →
5.1.48 11 Jul 2019 H1 M2 non-standard Yes Details →
8.0.17 07 Jun 2019 M2 non-standard Yes Details →
8.0.16 20 Mar 2019 M2 non-standard Yes Details →
8.0.15 28 Jan 2019 M3 non-standard Yes Details →
8.0.14 17 Dec 2018 M3 non-standard Yes Details →
8.0.13 27 Sep 2018 M3 non-standard Yes Details →
5.1.47 07 Aug 2018 H1 M2 non-standard Yes Details →
8.0.12 28 Jun 2018 H1 M3 non-standard Yes Details →
8.0.11 25 Mar 2018 H1 M3 non-standard Yes Details →
5.1.46 26 Feb 2018 H1 M2 non-standard Yes Details →
8.0.9-rc 24 Jan 2018 H1 M3 non-standard Yes Details →
5.1.45 22 Nov 2017 H1 M2 non-standard Yes Details →
8.0.8-dmr 26 Sep 2017 H1 M3 non-standard Yes Details →
5.1.44 29 Aug 2017 H1 M2 non-standard Yes Details →
5.1.43 06 Jul 2017 H1 M2 non-standard Yes Details →
8.0.7-dmr 15 Jun 2017 H1 M3 non-standard Yes Details →
5.1.42 17 Apr 2017 H1 M2 non-standard Yes Details →
6.0.6 23 Feb 2017 H1 M2 non-standard Yes Details →
5.1.41 14 Feb 2017 H1 M3 L1 non-standard Yes Details →
6.0.5 10 Oct 2016 H1 M2 non-standard Yes Details →
5.1.40 24 Sep 2016 H2 M3 L1 non-standard Yes Details →
6.0.4 12 Aug 2016 H1 M2 non-standard Yes Details →
6.0.3 14 Jun 2016 H1 M2 non-standard Yes Details →
5.1.39 04 May 2016 H2 M3 L1 non-standard Yes Details →
6.0.2 29 Mar 2016 H1 M2 non-standard Yes Details →
5.1.38 02 Dec 2015 H2 M3 L1 non-standard Yes Details →
5.1.37 06 Oct 2015 H2 M3 L1 non-standard Yes Details →
5.1.36 19 Jun 2015 H2 M3 L1 non-standard Yes Details →
5.1.32 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.1.3 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.0.4 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.1.9 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.1.21 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.1.19 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.1.13 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.1.14 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.1.26 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.1.4 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.0.3 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
3.1.11 20 Apr 2015 H2 M4 L1 — Yes Details →
5.1.35 20 Apr 2015 H2 M3 L1 non-standard Yes Details →
5.1.31 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.0.7 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.1.22 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.1.28 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.1.10 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.1.17 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.1.25 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
3.1.12 20 Apr 2015 H2 M4 L1 — Yes Details →
5.0.2 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.1.5 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.0.8 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
2.0.14 20 Apr 2015 H2 M4 L1 — Yes Details →
5.1.34 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.1.15 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
3.0.10 20 Apr 2015 H2 M4 L1 — Yes Details →
5.1.27 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.1.20 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.1.12 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.1.18 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.1.33 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.0.5 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.1.8 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.1.2 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.1.6 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
3.1.13 20 Apr 2015 H2 M4 L1 — Yes Details →
5.1.16 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
3.0.8 20 Apr 2015 H2 M4 L1 — Yes Details →
5.1.24 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.1.29 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.1.23 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.1.11 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
3.1.14 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.1.30 20 Apr 2015 H2 M4 L1 non-standard Yes Details →
5.1.1 20 Apr 2015 H2 M4 L1 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2022 7

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 mysql:mysql-connector-java

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-3258: Improper Privilege Management in MySQL Connectors Java 8.8 high 8.0.13 13 May 2022
CVE-2017-3523: Improper Access Control in MySQL Connectors Java 8.5 high 5.1.41 13 May 2022
CVE-2022-21363: Improper Handling of Insufficient Permissions or Privileges in MySQL Connectors Java 6.6 medium 8.0.28 20 Jan 2022
CVE-2017-3586: Oracle MySQL Connectors Java - Exposure of Sensitive Information 6.4 medium 5.1.42 13 May 2022
CVE-2019-2692: Privilege escalation in mysql-connector-java 6.3 medium 8.0.16 01 Jul 2020

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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:mysql-connector-java

Is mysql:mysql-connector-java safe to use?

Vulert records 8 vulnerabilities for mysql:mysql-connector-java in Maven: 0 critical, 2 high, 5 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

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

Vulert scores mysql:mysql-connector-java 69/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).

Is the latest version of mysql:mysql-connector-java affected?

No. 8.0.33, 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 mysql:mysql-connector-java should I use?

8.0.33 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 mysql:mysql-connector-java have?

8 vulnerabilities are recorded for mysql:mysql-connector-java in the Maven ecosystem: 0 critical, 2 high, 5 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new mysql:mysql-connector-java vulnerabilities disclosed?

0 vulnerabilities were recorded for mysql:mysql-connector-java in the last 12 months, and the oldest entry in this database dates to 01 Jul 2020. 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:mysql-connector-java 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:mysql-connector-java for upcoming vulnerabilities?

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