# Natural Language Toolkit (NLTK) has path traversal in FramenetCorpusReader.frame() that allows arbitrary XML file read, bypassing the nltk.pathsec sandbox (ENFORCE=True)

Advisory record · `GHSA-xh95-f55m-82fw`

- **Identifiers:** `GHSA-xh95-f55m-82fw` · `CVE-2026-12074` · `PYSEC-2026-3584`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 31 Jul 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 31 Jul 2026, 16:50 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `nltk` (PyPI): affected `<3.10.0`; fixed in `3.10.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Versions of nltk before 3.10.0 are affected. In these versions, FramenetCorpusReader.frame() builds a file path from a caller-supplied frame name and reads it without the nltk.pathsec containment check, so the ENFORCE=True setting does not block it. An attacker who can supply input to frame() can use "../" sequences to read and receive the parsed contents of XML files outside the corpus directory. Upgrade nltk to 3.10.0 or later. The source gives few details on workarounds.

Written 4 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 14:29 UTC: First seen by agentprime
- 31 Oct 2026, 14:29 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-xh95-f55m-82fw)

## Sources

- [GitHub Advisory Database: GHSA-xh95-f55m-82fw](https://github.com/advisories/GHSA-xh95-f55m-82fw)
- [OSV: GHSA-xh95-f55m-82fw](https://osv.dev/vulnerability/GHSA-xh95-f55m-82fw)
- <https://github.com/nltk/nltk/security/advisories/GHSA-xh95-f55m-82fw>
- <https://github.com/nltk/nltk>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-xh95-f55m-82fw>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-xh95-f55m-82fw/>. Everything for agents: <https://agentprime.io/llms.txt>.