How severe is CVE-2023-22102?

CVE-2023-22102 has a CVSS score of 8.3/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2023-22102?

CVE-2023-22102 affects the following packages: com.mysql:mysql-connector-j (Maven), mysql:mysql-connector-java (Maven). Ecosystems affected: Maven.

How do I fix CVE-2023-22102?

Update com.mysql:mysql-connector-j to 8.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-22102 is resolved across your whole dependency graph.

How do I detect CVE-2023-22102 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.mysql:mysql-connector-j, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2023-22102 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2023-22102 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-22102 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2023-22102?

CVE-2023-22102 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 63th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-22102?

CVE-2023-22102 is classified as CWE-284 (CWE-284). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2023-22102 published, and has it been updated?

CVE-2023-22102 was published on October 18, 2023 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2023-22102 — mysql-connector-j

HIGH

CVE-2023-22102 is a high-severity (CVSS 8.3) CWE-284 vulnerability in com.mysql:mysql-connector-j. A fix is available for com.mysql:mysql-connector-j — see the affected versions and patch details below.

MySQL Connectors takeover vulnerability

Published

Oct 18, 2023

Updated

Sep 10, 2026

Affected

2 pkgs

Patched

1 / 2

Exploits

None indexed

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-22102.

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs63th percentile — riskier than 63% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕com.mysql:mysql-connector-j☕mysql:mysql-connector-java

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Vulnerability in the MySQL Connectors product of Oracle MySQL (component: Connector/J). Supported versions that are affected are 8.1.0 and prior. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise MySQL Connectors. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in MySQL Connectors, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of MySQL Connectors. CVSS 3.1 Base Score 8.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H).

Affected Packages

2 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.mysql:mysql-connector-j`	all versions	8.2.0`com.mysql:mysql-connector-j:8.2.0`
☕Maven	`mysql:mysql-connector-java`	all versions	No fix

Affected Products

2 products · 2 configurations

Application

oncommand insightnetapp

all

Application

mysql connector\/joracle

≤ 8.1.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.mysql:mysql-connector-j, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.mysql:mysql-connector-j to 8.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-22102 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2023-22102 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

8.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

CWE Classification

CWE-284CWE-284

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

mysql-connector-j

4.7/10

Maintained5/10

Code-Review0/10

Branch-Protection0/10

Assessed Nov 2, 2026

Timeline

Disclosed

Oct 18, 2023

Last updated

Sep 10, 2026

Identifiers

CVE-2023-22102

References

Advisorynvd.nist.gov · CVE 2023 22102 Webgithub.com · 8.1.0...8.2.0 Websecurity.netapp.com · ntap 20231027 0007 Weboracle.com · cpuoct2023 Packagegithub.com · mysql connector j

Related vulnerabilities

This CVE is high severity; 2 of 8 other CVEs affecting mysql-connector-java are rated as high or higher (top: high).

CVE-2021-2471CVE-2015-2575CVE-2017-3523CVE-2018-3258CVE-2017-3589CVE-2017-3586CVE-2022-21363CVE-2019-2692

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedSep 10, 2026

CVE-2023-22102 — mysql-connector-j

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2023-22102 in your dependencies?