EM-20261113-KEO8
VulnerabilityHigh severity
NLTK Vulnerability (CVE-2026-126295)
CVE-2026-126295
Status
Developing
Since : signals keep joining.
- First Signal
- Nov 13 10:17 UTCC6 NVD CVE API 2.0
- Page Born
- Nov 13 23:20 UTCsecond source joined
- Last Signal
- Nov 13 23:20 UTC2 days before snapshot
- Sources
- 20 official · 2 research, news or crowd
- Open For
- 13 hoursso far
Life Of This Page
- 1BornA second, independent source names it.
- 2Developing · NowNew signals join; severity can move.
- 3ConfirmedNot yetCISA KEV lists it, or exploitation in the wild is reported.
- 4ResolvedNot yetPast the fix deadline and 14 days with no new signal.
- 5ArchivedNot yet30 days after resolved. Read only; the link keeps working. Reopens if it comes back.
The ID never changes, and earlier addresses keep working. A correction is logged, never overwritten. If two pages turn out to be one incident, the later one points to the earlier.
Vulnerability Lifecycle
- Disclosed: reachedNov 13 10:17 UTCC6 NVD published
- Scored: reachedNov 13 10:17 UTCCVSS 7 · EPSS 0.2%
- Exploited: not yetNot yetNo exploitation reported
- Advisories: not yetNot yetNone yet
- Vendor Response: not yetNot yetNone in sources yet
- Resolved: not yetNot yetAfter 14 quiet days
Timeline
Point at a mark to read it. Squares are signals, colored by severity; every one is also listed under Signals.
Signals
- GHSA-fg9w-wfp5-j933 / CVE-2026-126295: NLTK: BllipParser passes caller-supplied model paths to the bllipparser C extension with no pathsec check, enabling arbitrary read (opens source in a new tab) pip:nltk Med severityDatabaseC26 GitHub Advisory Database
- CVE-2026-126295 (CVSS 7) (opens source in a new tab) NLTK from 3.10.0 before 3.10.4 contains an arbitrary file read vulnerability in BllipParser that allows attackers to open files outside NLTK data roots by supplying unvalidated model paths. Attackers controlling… High severityDatabaseC6 NVD CVE API 2.0