CVE-2026-91992

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreHIGH confidence

Score 5.9 from GitHub Security Advisory (severity: HIGH) published 2026-09-15. a secondary CVSS source baseline 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Tornado before 6.5.7 contains a credential leak vulnerability in CurlAsyncHTTPClient where pycurl handles are reused across requests without proper state clearing. Attackers can obtain sensitive credentials by issuing requests through the same client instance, allowing TLS certificates or proxy authentication to persist across unintended requests.

CVSS v3
5.9
EG Score
5.9(high)
EG Risk
43(Track)
EG Risk 43/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity59% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
11%
KEV
Not listed

Published

September 15, 2026

Last Modified

September 17, 2026

Advisory Details (2)

Auto-updated Sep 15, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

Tornado before 6.5.7 Credential Leak via Handle Reuse | Advisories | VulnCheck

https://www.vulncheck.com/advisories/tornado-before-6.5.7-credential-leak-via-handle-reuse
github Patch Available🟡 PoC Available

CurlAsyncHTTPClient leaks per-request credentials on handle reuse · Advisory · tornadoweb/tornado · GitHub

https://github.com/tornadoweb/tornado/security/advisories/GHSA-pw6j-qg29-8w7f

Vendor Advisories for CVE-2026-91992(1)

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

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
tornado0.2 ... 6.5b1 (82 versions)6.5.7—

Weakness Classification(1)

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

Data Freshness Timeline

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

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 17:49 UTCEG score recompute
  3. 2026-09-18 17:49 UTCGHSA enrichment
  4. 2026-09-17 19:32 UTCEPSS rescore
  5. 2026-09-17 18:08 UTCEG score recompute
  6. 2026-09-17 18:08 UTCGHSA enrichment
  7. 2026-09-17 15:29 UTCEG score recompute
  8. 2026-09-17 15:29 UTCGHSA enrichment
  9. 2026-09-17 13:29 UTCEG score recompute
  10. 2026-09-17 13:29 UTCGHSA enrichment
  11. 2026-09-16 14:09 UTCEPSS rescore
  12. 2026-09-16 13:45 UTCEG score recompute
  13. 2026-09-16 13:44 UTCGHSA enrichment
  14. 2026-09-15 16:32 UTCEG score recompute
  15. 2026-09-15 15:23 UTCEG score recompute
  16. 2026-09-15 15:22 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-91992?
CVE-2026-91992 is a medium vulnerability published on September 15, 2026. Tornado before 6.5.7 contains a credential leak vulnerability in CurlAsyncHTTPClient where pycurl handles are reused across requests without proper state clearing. Attackers can obtain sensitive credentials by issuing requests through the same client instance, allowing TLS certificates or proxy…
When was CVE-2026-91992 disclosed?
CVE-2026-91992 was first published in the National Vulnerability Database on September 15, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-91992 actively exploited?
CVE-2026-91992 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 89.0% of all scored CVEs.
What is the CVSS score of CVE-2026-91992?
CVE-2026-91992 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-91992?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-91992, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-91992?

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

Start Free Scan →Browse All CVEs