nltk IPIPANCorpusReader Symlink Arbitrary File Read (CVE-2026-62383) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-62383

nltk IPIPANCorpusReader Symlink Arbitrary File Read

Answer in brief

CVE-2026-62383 records a Unknown severity vulnerability in nltk IPIPANCorpusReader Symlink Arbitrary File Read. The current sources do not mark it as known exploited. The current feed maps nltk/nltk (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 22, 2026Updated Aug 22, 2026Source checked Aug 22, 2026First seen by HOL Aug 22, 2026Material review Aug 22, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps nltk/nltk (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
nltk/nltkgeneric	>=3.10.0 <3.10.2	3.10.2

Recommended response

Check inventory. Check lockfiles and deployed manifests for nltk/nltk.
Review the reported fix. Update nltk/nltk to 3.10.2 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 22, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 22, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 22, 2026

Sources and claim methodology

Upstream source description

nltk versions before 3.10.2 contain a symlink-based arbitrary file read vulnerability in IPIPANCorpusReader methods that bypass nltk.pathsec validation entirely. Attackers can place a symlink in the corpus root directory and read arbitrary files accessible to the process by calling channels(), domains(), categories(), or fileids() methods with the symlink filename.

Quoted source text, attributed separately from HOL analysis.