Skip to main content
Mallory
UnratedVulnerability

CVE-2026-15367: Path traversal in NLTK maximum entropy parameter loading and saving

Updated 5 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-15367CWE-22

NLTK's load_maxent_params() and save_maxent_params() accept caller-controlled tab_dir values and access model parameter files using built-in open() without nltk.pathsec validation. This permits filesystem access outside permitted NLTK data directories, even when pathsec.ENFORCE is enabled. Depending on which API is exposed, exploitation allows reading model parameter files or creating and overwriting the expected parameter files in attacker-selected directories, subject to the process's filesystem permissions.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Applications exposing these APIs to attacker-influenced directory values may permit unauthorized disclosure of model parameters or creation and modification of files outside intended NLTK data directories. File operations are constrained to the parameter filenames used by the APIs and the filesystem permissions of the application process. Enabling pathsec.ENFORCE alone does not prevent exploitation.

Mitigation

If you can’t patch tonight, do this now.

No interim workaround is explicitly specified. Applications must not rely on pathsec.ENFORCE to protect these vulnerable APIs from attacker-controlled tab_dir values.

Remediation

Patch, then assume compromise.

Upgrade to NLTK 3.10.4 or later, identified by the affected-package metadata as the overall fixed version. The load-side fix is included in releases since 3.9.4, but that fix alone does not establish protection for the save API. The save-side fix validates tab_dir and writes parameter files through pathsec.open.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-15367 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-15367 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-15367?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-15367.
Is there a patch for CVE-2026-15367?
Upgrade to NLTK 3.10.4 or later, identified by the affected-package metadata as the overall fixed version. The load-side fix is included in releases since 3.9.4, but that fix alone does not establish protection for the save API.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.