CVE-2026-62388

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

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

NLTK versions before 3.10.0 default to ENFORCE=False in pathsec.py, causing all security validation functions to emit warnings instead of raising exceptions. Attackers can bypass path traversal and pickle deserialization protections by exploiting the disabled security controls that are only active when manually enabled.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
38(Track)
EG Risk 38/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
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

August 22, 2026

Last Modified

August 22, 2026

Advisory Details (2)

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

NLTK before 3.10.0 Insecure Default Configuration pathsec | Advisories | VulnCheck

https://www.vulncheck.com/advisories/nltk-before-insecure-default-configuration-pathsec
github Patch Available🟡 PoC Available

[CWE-1188] Default ENFORCE=False Disables All pathsec Security Controls · Advisory · nltk/nltk · GitHub

https://github.com/nltk/nltk/security/advisories/GHSA-p3m8-78j2-g5p3

Vendor Advisories for CVE-2026-62388(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 17× 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-08-26 14:46 UTCEPSS rescore
  2. 2026-08-26 12:48 UTCGHSA enrichment
  3. 2026-08-26 01:08 UTCEG score recompute
  4. 2026-08-26 01:08 UTCGHSA enrichment
  5. 2026-08-25 13:49 UTCEPSS rescore
  6. 2026-08-25 13:26 UTCGHSA enrichment
  7. 2026-08-25 01:45 UTCEG score recompute
  8. 2026-08-25 01:45 UTCGHSA enrichment
  9. 2026-08-24 14:05 UTCEG score recompute
  10. 2026-08-24 14:05 UTCGHSA enrichment
  11. 2026-08-24 02:25 UTCGHSA enrichment
  12. 2026-08-23 14:45 UTCGHSA enrichment
  13. 2026-08-23 03:05 UTCEG score recompute
  14. 2026-08-23 03:05 UTCGHSA enrichment
  15. 2026-08-22 15:24 UTCEG score recompute
  16. 2026-08-22 14:26 UTCEG score recompute
  17. 2026-08-22 14:25 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-62388?
CVE-2026-62388 is a high vulnerability published on August 22, 2026. NLTK versions before 3.10.0 default to ENFORCE=False in pathsec.py, causing all security validation functions to emit warnings instead of raising exceptions. Attackers can bypass path traversal and pickle deserialization protections by exploiting the disabled security controls that are only active…
When was CVE-2026-62388 disclosed?
CVE-2026-62388 was first published in the National Vulnerability Database on August 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62388 actively exploited?
CVE-2026-62388 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 74.1% of all scored CVEs.
What is the CVSS score of CVE-2026-62388?
CVE-2026-62388 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-62388?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62388, 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

Explore the affected products and dependency analysis for CVE-2026-62388

Explore →

Is Your Infrastructure Affected by CVE-2026-62388?

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

Start Free Scan →Browse All CVEs