Skip to main content
VulnerabilityPublished

CVE-2026-126296: NLTK · Path Traversal in save_maxent_params / load_maxent_params Allow Arbitrary File READ/WRITE

Affects nltkSource GCVE Database

0
Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-126296· Medium 6.3

Not known to be exploited · CVSS 6.3 Medium : upgrade to 3.10.4 when convenient.

Data as of 16 Nov 2026, 15:34 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.06.3
CNA (VulnCheck)CVSS 3.14.8
Patch
Available – fixed in 3.10.4
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade nltk to 3.10.4.

Affected software

ProductAffectedFixed in
PyPInltkAffected
  • <3.10.4
Fixed in
  • 3.10.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available and has been merged into NLTK. The load_maxent_params() function fix is included in all releases since version 3.9.4, and the save_maxent_params() fix is included starting from version 3.10.4. Users should upgrade to NLTK version 3.10.4 or later to remediate this vulnerability. No additional mitigation is required if the software is updated accordingly.

Description

NLTK's save_maxent_params() and load_maxent_params() functions suffer from a path traversal vulnerability that allows arbitrary file read and write outside the intended directories. This occurs because these functions use the Python built-in open() directly on paths derived from a user-controlled argument without enforcing NLTK's pathsec security checks. The vulnerability bypasses the filesystem sandboxing intended by pathsec.ENFORCE, potentially allowing attackers to read or overwrite files outside permitted directories. The issue affects NLTK versions prior to 3.10.4. A fix has been merged and is included starting from version 3.10.4.

References

Community reviews

Loading reviews…