How severe is CVE-2019-2435?

CVE-2019-2435 has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-2435?

CVE-2019-2435 affects the following packages: mysql-connector-python (PyPI), mysql-connector-python (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2019-2435?

Update mysql-connector-python to 8.0.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-2435 is resolved across your whole dependency graph.

How do I detect CVE-2019-2435 in my PyPI dependencies?

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

How do I mitigate CVE-2019-2435 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-2019-2435 actively exploited in the wild?

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

CVE-2019-2435 has an EPSS (Exploit Prediction Scoring System) score of 2.5%, placing it in the 85th 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-2019-2435 published, and has it been updated?

CVE-2019-2435 was published on May 13, 2022 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.

🐍

🐍 PyPI

Not in CISA KEV

HIGH severity

CVE-2019-2435 — mysql-connector-python

HIGH

CVE-2019-2435 is a high-severity (CVSS 8.1) vulnerability in mysql-connector-python. A fix is available for mysql-connector-python — see the affected versions and patch details below.

Improper Access Control in MySQL Connector Python

Also known asPYSEC-2026-683

Published

May 13, 2022

Updated

Sep 10, 2026

Affected

2 pkgs

Patched

1 / 2

Exploits

None indexed

Exploitation data as of Nov 3, 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-2019-2435.

EPSS Exploitation Probability

via FIRST.org ↗

2.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs85th percentile — riskier than 85% 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

🐍mysql-connector-python🐍mysql-connector-python

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

Description

Vulnerability in the MySQL Connectors component of Oracle MySQL (subcomponent: Connector/Python). Supported versions that are affected are 8.0.13 and prior and 2.1.8 and prior. Easily exploitable vulnerability allows unauthenticated attacker with network access via TLS to compromise MySQL Connectors. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all MySQL Connectors accessible data as well as unauthorized access to critical data or complete access to all MySQL Connectors accessible data. CVSS 3.0 Base Score 8.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N).

Affected Packages

2 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`mysql-connector-python`	≥ 8.0.0&&< 8.0.19	8.0.19`pip install --upgrade 'mysql-connector-python==8.0.19'`
🐍PyPI	`mysql-connector-python`	≥ 2.1.0	No fix

Affected Products

4 products · 6 configurations

Application

active iq unified managernetapp

≥ 9.5

range

Application

oncommand workflow automationnetapp

all

Application

snapcenternetapp

all

Application

mysql connectorsoracle

≥ 8.0.0 && ≤ 8.0.13

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-connector-python, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mysql-connector-python to 8.0.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-2435 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.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-2435 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

8.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Raw vector

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

Weaponization

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

OpenSSF Scorecard

Package health score

mysql-connector-python

4.0/10

Code-Review0/10

Maintained10/10

Branch-Protection0/10

Assessed Oct 26, 2026

Timeline

Disclosed

May 13, 2022

Last updated

Sep 10, 2026

Identifiers

CVE-2019-2435

PYSEC-2026-683

References

Advisorynvd.nist.gov · CVE 2019 2435 Websecurity.netapp.com · ntap 20190118 0002 Weblists.opensuse.org · msg00044 Weblists.opensuse.org · msg00053 Weboracle.com · cpujan2019 5072801 Websecurityfocus.com Packagegithub.com · mysql connector python

Related vulnerabilities

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

CVE-2024-21272CVE-2017-3590

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedSep 10, 2026

CVE-2019-2435 — mysql-connector-python

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-2019-2435 in your dependencies?