NLTK · GHSA-w2j9-qh3j-4h63 · Package
NO FIX YET · SEE WHAT TO DO
NLTK's chat80 sql_query function follows symbolic links, so a symlink planted in a trusted NLTK data directory can point it at SQLite databases outside the sandbox. An attacker who can write into that data root can read those database files.
first public Nov 13, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Only teams that call nltk.sem.chat80.sql_query and let someone other than the team write into the NLTK data root. Exposure depends on whether the data directory is writable by untrusted users. unknown whether other NLTK functions are affected.
Not affected if default-config, no-chat80-use
Who cares nltk, python
pip show nltk; affected range is 3.9.4 up to but not including 3.10.4.nltk.sem.chat80.sql_query that run on paths you do not fully control.nltk 3.10.4 (the advisory's stated range ends before 3.10.4; the duplicate advisory GHSA-xmfg-f9cm-w86q is the live record).This advisory has been withdrawn because it is a duplicate of GHSA-xmfg-f9cm-w86q. This link is maintained to preserve external references.
NLTK from 3.9.4 before 3.10.4 contains a symlink following vulnerability in nltk.sem.chat80.sql_query() that bypasses the pathsec data-root sandbox containment check. Attackers who can write into a trusted NLTK data root can plant a symbolic link to read SQLite databases outside the sandbox.
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
GitHub Advisory Database, CC-BY 4.0. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.