ssl.get_server_certificate(addr, ca_certs=...) verifies the chain but never the identity
- Exploited
- No known exploitation
- Fix
- Fixed in 3.16.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.16.0.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The ssl.get_server_certificate() function verifies the certificate chain but not the certificate's identity when ca_certs is supplied, so a certificate for a different identity can be accepted. An attacker can reach this remotely over the network, without logging in or any user action, but the CVSS rates it as having no confidentiality, integrity, or availability impact.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
When ca_certs parameter was supplied to ssl.get_server_certificate() function, the identity of the certificate is not checked.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity0/10CVSS 0.0
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 22 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 3.16.0.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- Python Software Foundation CPython
fixed in 3.16.0
Evidence 4
- Advisory
- Patch
- Report
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-19552
Is CVE-2026-19552 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-19552?
CPython: before 3.16.0.Source: cve.now feed data
How do I fix CVE-2026-19552?
Upgrade to a fixed version: 3.16.0.Source: cve.now feed data