Quick answers
- Is CVE-2017-3590 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2017-3590 being exploited in the wild.
- How severe is CVE-2017-3590?
- Low severity, with a CVSS score of 3, published 2 July 2026.
- Which products and versions are affected?
- mysql-connector-python (PyPI) ECOSYSTEM:introduced=0,last_affected=2.1.5.
- Is there a fix for CVE-2017-3590?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2017-3590 attacked?
- It is attacked with local access.
- Am I affected by CVE-2017-3590?
- Check whether you run mysql-connector-python (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This vulnerability in MySQL Connector/Python (versions 2.1.5 and earlier) allows a local attacker with low-level system privileges to perform unauthorized data modification. The vulnerability requires local system access and low-level privileges but no special interaction or elevated permissions; it results in integrity impact through unauthorized update, insert, or delete operations on data accessible to the connector component. The CVSS 3.0 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N) indicates local attack vector, low complexity, and impact limited to integrity. The root cause appears related to insufficient access controls on connector data or resources.
Affected products
- Oracle MySQL Connector/Python 2.1.5 and earlier
Identifiers
- CVE-2017-3590
- GHSA-2cf3-g243-hhfx
- PYSEC-2026-682
Timeline
- 2017-04-24: disclosed
- 2022-05-13: advisory