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.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.5 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | 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