CVE-2026-126296: NLTK · Path Traversal in save_maxent_params / load_maxent_params Allow Arbitrary File READ/WRITE
Affects acronymSource GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 6.3 Medium : upgrade to 2.0.0_6 when convenient.
Data as of 17 Nov 2026, 19:05 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 6.3 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 4.8 |
- Patch
- Available – fixed in 2.0.0_6
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 16 Nov 2026.
What to do
Upgrade acronym to 2.0.0_6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewacronympkg:brew/acronymOther threats | Affected
| Fixed in
|
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. The load_maxent_params() function fix is included in NLTK releases since version 3.9.4 (including 3.10.3). The save_maxent_params() fix has been merged on the develop branch but is not yet released. Users should upgrade to NLTK version 3.9.4 or later to receive the load_maxent_params() fix and monitor for the next release that includes the save_maxent_params() fix. Until then, avoid passing untrusted input to the tab_dir argument or disable pathsec enforcement if it causes issues. The vendor manages remediation through official releases.
Description
NLTK's save_maxent_params() and load_maxent_params() functions contain a path traversal vulnerability that allows arbitrary file read and write outside the intended directories. This occurs because these functions use Python's built-in open() directly on paths derived from a user-controlled tab_dir argument, bypassing NLTK's pathsec security mechanism. The vulnerability enables attackers who can control tab_dir to read or overwrite files outside the permitted filesystem boundaries. The issue affects versions prior to 3.9.4 for load_maxent_params and is fixed in 3.9.4 and later for loading; the save functionality fix is merged but not yet released. The CVE assigned is CVE-2026-15367, with a CVSS 4.0 score of 6.3 (medium severity).
References
- github.com/nltk/nltk/security/advisories/GHSA-59f9-gqg8-mqpj (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-126296 (opens in a new tab)
- github.com/nltk/nltk/pull/3759 (opens in a new tab)
- github.com/nltk/nltk/commit/2a92b71827d754ae8920261e7ed0c4bb283ab2d7 (opens in a new tab)
- github.com/nltk/nltk (opens in a new tab)
- github.com/nltk/nltk/releases/tag/v3.10.4 (opens in a new tab)
- vulncheck.com/advisories/nltk-before-3.10.4-path-traversal-via-save-maxent-params-and-load-maxent-params (opens in a new tab)