
Security advisory • CPython TLS certificate validation • CVE-2026-115557[3]
CPython adds an eMudhra certificate-key denylist as defense in depth[1][2]
CPython merged a safeguard that rejects TLS chains containing affected eMudhra intermediate CA public keys, including cross-signed certificates that reuse a compromised key. The project describes the change as defense in depth while trust-store updates propagate; no released fixed CPython version is established by the captured sources.[1][2][3][5]
Reporting cutoff: 2026-10-25T07:39:05-04:00 (EDT; America/New_York) / 2026-10-25T11:39:05Z (UTC).[6]
Small-business decision: determine whether Python TLS clients perform certificate verification, keep verification enabled, and wait for an explicit fixed release or downstream package statement before declaring the CPython denylist deployed. Continue applying supported operating-system, container, CA-bundle and Python updates; a merged commit is not proof that an installed runtime contains the safeguard.[1][2]
What changed
The CPython issue proposes a small _ssl denylist that matches DER-encoded SubjectPublicKeyInfo during certificate verification, so a cross-signed certificate reusing an affected key is blocked.[1]
The direct callback applies when verification is enabled with CERT_OPTIONAL or CERT_REQUIRED; CERT_NONE is unaffected. That boundary is not a reason to disable certificate verification.[1]
The main pull request merged to CPython’s main branch at 2026-10-24T05:40:50Z.[2]
Severity and classification need context
The Python CNA data carried by NVD identifies CPython’s ssl module, an affected expression from version 0 up to but not including 3.16.0, and CVSS v4 9.4 Critical.[3]
Classification nuance: Debian’s tracker lists an open, unimportant entry for its tracked python3.11 package and says, “Security feature work, not a vulnerability itself.” This differs from the Python CNA’s Critical classification; the article preserves both boundaries rather than presenting the score as proof of exploitation.[3][4]
GitHub’s advisory is marked unreviewed and contains no vulnerability package records in the captured API response, so it does not establish a released patched package version.[5]
Exposure predicate
A relevant case requires a Python TLS client that performs certificate verification, encounters a chain using one of the affected eMudhra intermediate public keys, and has not yet received effective distrust through its operating-system, container, bundled CA store or CPython runtime. This is a practical inference from the project’s stated enforcement boundary, not a claim that every Python application is exposed.[1][2]
Practical guidance
- Identify the verifying workload. Check whether the Python TLS client performs certificate verification; the denylist runs during certificate verification.[1]
- Keep verification enabled. Do not switch to
CERT_NONE; the project says the denylist callback runs only when certificate verification is enabled.[1] - Use supported supplier updates. Apply supported operating-system, container, CA-bundle and Python updates from the deployment’s supplier, but require release notes or package guidance that explicitly identifies the remediation before calling the CPython denylist present.[1][2]
- Do not equate merge with deployment. The main-branch pull request is merged, but the captured sources do not name a released CPython version containing the change.[2][3][5]
What remains unknown
The captured sources do not establish which released CPython version first contains the direct denylist, which downstream packages have backported it, how many deployments could encounter an affected chain, or whether compromised keys were used specifically against Python clients. This article does not claim active exploitation or compromise of CPython infrastructure.[1][2][3][5]
Sources
- CPython issue 160040 — distrust compromised eMudhra intermediate CA keys.
- CPython pull request 160042 — merged denylist change.
- NVD — CVE-2026-115557 (Python CNA data).
- Debian Security Tracker — CVE-2026-115557.
- GitHub Advisory Database — GHSA-x547-2835-q547.
- Time.gov — public clock reference for the recorded reporting cutoff.
