# CVE-2026-70626: NLTK before 3.9.4 Symlink Escape via CorpusReader

> Local attackers can read arbitrary files outside the corpus root by placing symlinks inside the corpus directory in NLTK.

- **Severity:** High 8.6 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Aug 2026
- **Updated:** 24 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-70626, ECHO-9e81-b61d-422b, GHSA-r6gq-whwq-mvg9, MINI-7qrv-vmhw-6pwf, PYSEC-2026-3732, UBUNTU-CVE-2026-70626

## What is CVE-2026-70626?

CVE-2026-70626 is a high-severity path traversal vulnerability in nltk, published on 22 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

NLTK versions before 3.9.4 contain a symlink escape vulnerability in CorpusReader.open() that allows local attackers to read arbitrary files outside the corpus root. The vulnerability exists because path validation is lexical and does not account for symlink resolution, enabling attackers to place symlinks inside the corpus root to access files outside the intended boundary.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2026-70626?

3 open source packages ship an affected version, including nltk. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nltk` | PyPI | All versions | 3.9.4 |
| `nltk` | PyPI | All versions | 3.9.4 |
| `nltk` | PyPI | All versions | 3.9.4 |

Products: Nltk Nltk.

## How do I fix CVE-2026-70626?

Upgrade nltk to 3.9.4 or later.

## Is CVE-2026-70626 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-70626 exists.

## Other vulnerabilities in nltk

- [CVE-2026-0848](https://insights.sbomify.com/CVE-2026-0848/): Arbitrary Code Execution in NLTK StanfordSegmenter via Untrusted JAR Loading (critical 10.0)
- [CVE-2025-14009](https://insights.sbomify.com/CVE-2025-14009/): Zip Slip Vulnerability in nltk/nltk Leading to Remote Code Execution (critical 10.0)
- [CVE-2026-78683](https://insights.sbomify.com/CVE-2026-78683/): NLTK before 3.10.0 Remote Code Execution via Unsafe Pickle Deserialization (critical 9.4)
- [CVE-2026-79657](https://insights.sbomify.com/CVE-2026-79657/): NLTK before 3.10.3 Remote Code Execution via Unsafe Pickle Deserialization (critical 9.3)
- [CVE-2026-79675](https://insights.sbomify.com/CVE-2026-79675/): NLTK before 3.10.3 JVM Argument Injection via Per-Call Options (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-70626 and fix it if it is affected.

What it is: CVE-2026-70626 is a high-severity path traversal vulnerability in nltk, published on 22 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-70626 exists.

Affected packages and fixed versions:
- nltk (PyPI): affected all versions; fixed in 3.9.4
- nltk (PyPI): affected all versions; fixed in 3.9.4
- nltk (PyPI): affected all versions; fixed in 3.9.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-70626/ (Markdown: https://insights.sbomify.com/CVE-2026-70626/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-70626
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-70626
- OSV: https://osv.dev/vulnerability/CVE-2026-70626

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-70626/
Summaries are generated and may contain mistakes; the official description above is the record.