How severe is CVE-2022-21363?

CVE-2022-21363 has a CVSS score of 6.6/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-21363?

CVE-2022-21363 affects the following packages: mysql:mysql-connector-java (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-21363?

Update mysql:mysql-connector-java to 8.0.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-21363 is resolved across your whole dependency graph.

How do I detect CVE-2022-21363 in my Maven dependencies?

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

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2022-21363 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-21363 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-2022-21363?

CVE-2022-21363 has an EPSS (Exploit Prediction Scoring System) score of 1.4%, placing it in the 72th 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.

When was CVE-2022-21363 published, and has it been updated?

CVE-2022-21363 was published on January 19, 2022 and was last updated on August 12, 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

MEDIUM severity

CVE-2022-21363 — mysql-connector-java

MEDIUM

CVE-2022-21363 is a medium-severity (CVSS 6.6) vulnerability in mysql:mysql-connector-java. A fix is available for mysql:mysql-connector-java — see the affected versions and patch details below.

Improper Handling of Insufficient Permissions or Privileges in MySQL Connectors Java

Also known asGHSA-g76j-4cxx-23h9

Published

Jan 19, 2022

Updated

Aug 12, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 11, 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-2022-21363.

EPSS Exploitation Probability

via FIRST.org ↗

1.4%probability of exploitation in next 30 days

Lower Risk-0.01%

Lower risk than most CVEs72th percentile — riskier than 72% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2022-21363 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

☕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.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Connectors. Successful attacks of this vulnerability can result in takeover of MySQL Connectors. CVSS 3.1 Base Score 6.6 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H).

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`mysql:mysql-connector-java`	all versions	8.0.28`mysql:mysql-connector-java:8.0.28`

Affected Products

2 products · 2 configurations

Application

mysql connectorsoracle

≥ 8.0.0 && ≤ 8.0.27

range

Application

quarkusquarkus

< 2.7.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 mysql:mysql-connector-java, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mysql:mysql-connector-java to 8.0.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-21363 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat build of Quarkus 2.7.5	`mysql-connector-java`	RHSA-2022:4623
Red Hat Fuse 7.11	`mysql-connector-java`	RHSA-2022:5532
RHPAM 7.13.1 async	`mysql-connector-java`	RHSA-2022:6813

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-21363 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.6/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

High

Privileges Required

High

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

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

Weaponization

No known public exploit tooling found.

Timeline

Disclosed

Jan 19, 2022

Last updated

Aug 12, 2026

Identifiers

CVE-2022-21363

GHSA-g76j-4cxx-23h9

References

Advisorygithub.com Advisorynvd.nist.gov Weboracle.com

Related vulnerabilities

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

CVE-2023-22102CVE-2021-2471CVE-2015-2575CVE-2017-3523CVE-2018-3258CVE-2017-3589CVE-2017-3586CVE-2019-2692

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedAug 12, 2026

CVE-2022-21363 — mysql-connector-java

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

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2022-21363 in your dependencies?