CVE-2026-19552

UNRATEDCVSS · not yet scored

Also known asEUVD-2026-120066 (ENISA EUVD) · GHSA-hrvr-m27m-jc99 (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

When ca_certs parameter was supplied to ssl.get_server_certificate() function, the identity of the certificate is not checked.

CVSS
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.3%
EPSS %ILE
24th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 9, 2026

Last Modified

November 12, 2026

References (5)

Vendor Advisories for CVE-2026-19552(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 3 ecosystems)
Debian:14(2)
PackageVulnerable rangeFix by version rangeDependents
python3.143.14.0-1 ... 3.14.9-1 (32 versions)
  • every version on: no fix on record
—
python3.153.15.0-1 ... 3.15.2-1 (17 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python3.113.11.2-6 ... 3.11.9-1 (29 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python3.133.13.11-1 ... 3.13.9-1 (15 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 18× in last 7d / 18× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 17:30 UTCGHSA enrichmentGHSA-hrvr-m27m-jc99 · GitHub severity LOW
  2. 2026-11-12 16:43 UTCEchelonGraph re-scored
  3. 2026-11-12 16:43 UTCGHSA enrichmentGHSA-hrvr-m27m-jc99 · GitHub severity LOW
  4. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  5. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  6. 2026-11-11 01:27 UTCGHSA enrichmentGHSA-hrvr-m27m-jc99 · GitHub severity LOW
  7. 2026-11-11 01:27 UTCNVD update
  8. 2026-11-11 00:35 UTCEchelonGraph re-scored
  9. 2026-11-11 00:35 UTCGHSA enrichmentGHSA-hrvr-m27m-jc99 · GitHub severity LOW
  10. 2026-11-11 00:34 UTCMITRE cvelistV5
  11. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  12. 2026-11-10 01:27 UTCGHSA enrichmentGHSA-hrvr-m27m-jc99 · GitHub severity LOW
  13. 2026-11-10 01:26 UTCNVD update
  14. 2026-11-10 00:35 UTCGHSA enrichmentGHSA-hrvr-m27m-jc99 · GitHub severity LOW
  15. 2026-11-09 21:15 UTCGHSA enrichmentGHSA-hrvr-m27m-jc99 · GitHub severity LOW
  16. 2026-11-09 21:14 UTCMITRE cvelistV5
  17. 2026-11-09 15:45 UTCGHSA enrichmentGHSA-hrvr-m27m-jc99 · GitHub severity LOW
  18. 2026-11-09 15:26 UTCNVD update
  19. 2026-11-09 15:00 UTCENISA EUVD ID recordedEUVD-2026-120066 · Source: ENISA EUVD
  20. 2026-11-09 14:20 UTCEchelonGraph re-scored
  21. 2026-11-09 14:20 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(4)

What is CVE-2026-19552?
CVE-2026-19552 is a vulnerability whose severity is not yet rated; its CVE record was published on November 9, 2026. When ca_certs parameter was supplied to ssl.get_server_certificate() function, the identity of the certificate is not checked.
When was the CVE record for CVE-2026-19552 published?
The CVE record for CVE-2026-19552 was published on November 9, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 12, 2026; the record at its source may have been updated since.
Is CVE-2026-19552 actively exploited?
CVE-2026-19552 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (24th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-19552?
A fix for CVE-2026-19552 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-19552 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-19552

Explore →

Is Your Infrastructure Affected by CVE-2026-19552?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs