Python up to 3.15.x SSL ssl.get_server_certificate ca_certs certificate validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.6 | $0-$5k | 0.00+ |
Summary
A vulnerability identified as problematic has been detected in Python up to 3.15.x. This affects the function ssl.get_server_certificate of the component SSL. Performing a manipulation of the argument ca_certs results in certificate validation.
This vulnerability is known as CVE-2026-19552. Remote exploitation of the attack is possible. No exploit is available.
You should upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in Python up to 3.15.x. This affects the function ssl.get_server_certificate of the component SSL. The manipulation of the argument ca_certs with an unknown input leads to a certificate validation vulnerability. CWE is classifying the issue as CWE-295. The product does not validate, or incorrectly validates, a certificate. This is going to have an impact on integrity. The summary by CVE is:
When ca_certs parameter was supplied to ssl.get_server_certificate() function, the identity of the certificate is not checked.
It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-19552 since 08/11/2026. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1587.003 according to MITRE ATT&CK.
Upgrading to version 3.16.0 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 3.7VulDB Meta Temp Score: 3.6
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Certificate validationCWE: CWE-295 / CWE-287
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Python 3.16.0
Timeline
08/11/2026 CVE reserved11/09/2026 Advisory disclosed
11/09/2026 VulDB entry created
11/09/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Confirmed
CNA: PSF
CVE: CVE-2026-19552 (🔒)
GCVE (CVE): GCVE-0-2026-19552
GCVE (VulDB): GCVE-100-433155
Entry
Created: 11/09/2026 15:34Changes: 11/09/2026 15:34 (68)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.