cve.bz

CVE-2026-126295 NLTK 3.10.0 before 3.10.4 Arbitrary File Read via BllipParser Model Paths

7.0 highEPSS 0.2%Fix available

High (7.0) in nltk nltk. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in nltk 3.10.4.

On this page
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 parser_model, reranker_features, reranker_weights, or from_unified_model_dir() input can make the bllipparser C extension read sensitive files or block on FIFOs and devices.

Severity

CVSS 4.0

7.0 high
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:L/SC:N/SI:N/SA:N

CVSS 3.1

6.8 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
EPSS
0.2% estimated probability of exploitation activity in the next 30 days; 10th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
VulnCheck (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-126295 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126295?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126295?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-126295 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-126295

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-126295](https://cve.bz/cve/badge/CVE-2026-126295.svg)](https://cve.bz/cve/CVE-2026-126295)

HTML:

<a href="https://cve.bz/cve/CVE-2026-126295"><img src="https://cve.bz/cve/badge/CVE-2026-126295.svg" alt="CVE-2026-126295"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
nltkfrom 3.10.0 before 3.10.4

Fix and patched versions

  • nltk (PyPI): fixed in 3.10.4

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-fg9w-wfp5-j933PyPInltk>=3.10.0 <3.10.43.10.4

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON