Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-62385

nltk: NLTK: Information disclosure through path traversal

Overview

Published
22 Aug 2026
Modified
14 Oct 2026
High CVE
1 Registry packages
2 OS packages
3 Linux distributions
Yes Fix available

Description

NLTK versions before 3.10.0 contain a path traversal vulnerability in FramenetCorpusReader and NKJPCorpusReader that allows attackers to parse XML files outside the corpus root by supplying unsafe selectors or poisoned index state. Attackers can exploit frame_by_name, doc, lu, and header methods with crafted parameters to read arbitrary XML files accessible to the application.

Source: OX vulnerability database

Severity

7.5 · HIGH

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Weakness: CWE-73

Affected packages · 1

Packages affected by CVE-2026-62385
EcosystemPackageVulnerableFixed in
PyPI nltk <3.10.0 3.10.0

Open a package to see all its vulnerabilities.

Operating systems · 6 fixes

debian 4 releases · 1 package

affected 3 fixed 1
nltk
debian fixes for CVE-2026-62385
ReleasePackageFixed in
11 nltk affected
12 nltk affected
13 nltk affected
14 nltk 3.10.0-1

echo 1 release · 1 package

affected 1
nltk
echo fixes for CVE-2026-62385
ReleasePackageFixed in
nltk affected

minimos 1 release · 1 package

fixed 1
label-studio
minimos fixes for CVE-2026-62385
ReleasePackageFixed in
label-studio 1.23.1-r0

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.