CVE-2026-19552 json
ssl.get_server_certificate(addr, ca_certs=...) verifies the chain but never the identity
published 2d ago modified yesterday also EUVD-2026-120066
- cvss
- 0.0
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 24%
- public exploits
- 0
- none known
Summary
When ca_certs parameter was supplied to ssl.get_server_certificate() function, the identity of the certificate is not checked.
Patch / fix
- Python Software Foundation CPython 3.16.0a2
- github.com/python/cpython@8dde46e commit
- github.com/python/cpython#161507 pull request
Is CVE-2026-19552 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.31% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 0.0 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N |
| CNA | 4.0 | 0.0 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- Python Software Foundation CPython
References
-
github.com
/python/cpython/pull/161507
patch
-
github.com
/python/cpython/commit/8dde46eaa6baf5f027a7234845b20d50b509624e
patch
-
mail.python.org
/archives/list/security-announce@python.org/thread/SXBD6BGHDBTGM4KSUMQEWYIQ5RO4BQ76/
vendor-advisory
-
github.com
/python/cpython/issues/161503
issue-tracking
- openwall.com /lists/oss-security/2026/11/09/25
Sources
- CVE List CVE-2026-19552
- NVD CVE-2026-19552
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.