Quick answers
- Is CVE-2026-19552 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-19552 being exploited in the wild.
- How severe is CVE-2026-19552?
- Informational severity, published 9 November 2026.
- Which products and versions are affected?
- Python CPython 3.11, 3.12, 3.13, 3.14, 3.15, 3.16.
- Is there a fix for CVE-2026-19552?
- Yes: fixed in CPython 3.11 (via gh-161670), 3.12 (via gh-161671), 3.13, 3.14, 3.15, 3.16. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-19552 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-19552?
- Check whether you run Python CPython 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.
How to fix
- Fixed in: CPython 3.11 (via gh-161670), 3.12 (via gh-161671), 3.13, 3.14, 3.15, 3.16
Technical details
The ssl.get_server_certificate() function performs X.509 chain validation against the supplied ca_certs but omits hostname verification, allowing presentation of any valid certificate regardless of identity. The vulnerability requires network access and application use of the function with custom ca_certs parameter. An attacker can intercept connections and present a valid certificate for a different hostname, which the function accepts as legitimate.
Affected products
- Python CPython 3.11, 3.12, 3.13, 3.14, 3.15, 3.16
Timeline
- 2026-11-06: disclosed
- 2026-11-07: patched