CVE-2026-79674 nltk CVE debrief

Who should care

Organizations using NLTK versions before 3.10.3 should prioritize patching and monitoring to prevent potential attacks. This includes developers, security teams, and system administrators responsible for maintaining and securing systems that utilize NLTK. Additionally, operators of systems that rely on NLTK for natural language processing tasks should be aware of the potential risks and take steps to mitigate them. Vulnerability management and security teams should review the affected scope and severity to determine the necessary course of action. Affected product deployments should be identified and assigned an owner for follow-up to ensure timely remediation. Compensating controls should be reviewed for exposed systems while remediation is scheduled and verified. Monitoring, detection, and logs for exposed assets should be checked for extra review. Exceptions, retest remediated assets, and close the item only after evidence is documented. System administrators should verify and validate input data to prevent arbitrary corpus root paths. Limited evidence suggests that this vulnerability may be exploited in the wild, but defenders should take a cautious approach to mitigate potential risks. This may involve implementing additional security controls, such as restricting access to sensitive data and systems, and conducting regular security audits to identify potential vulnerabilities. By taking these steps, organizations can reduce the risk of exploitation and protect their systems from potential attacks. The CVE record was published on 2026-08-25T16:17:27.873Z and has not been modified since then. The NVD entry is currently Analyzed. AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-08-25T16:17:27.873Z and has not been modified since then. The NVD entry is currently Analyzed. AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-08-25T16:17:27.873Z and has not been modified since then. The NVD entry is currently Analyzed. AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-08-25T16:17:27.873Z and has not be

Technical summary

NLTK versions before 3.10.3 contain a path sandbox bypass vulnerability in corpus-reader constructors. Attackers can supply arbitrary corpus root paths to LinThesaurusCorpusReader and PanLexLiteCorpusReader constructors to access filesystem content and SQLite databases outside the pathsec sandbox boundary. This vulnerability has a HIGH CVSS score of 8.8, indicating a high level of severity. Affected systems should be identified and patched to prevent potential attacks.

Defensive priority

High-priority defensive actions are required due to the HIGH CVSS score of 8.8. Affected systems should be identified and patched to prevent potential attacks.

Recommended defensive actions

• Identify and inventory all systems using NLTK versions before 3.10.3
• Apply patches or updates to NLTK version 3.10.3 or later
• Monitor systems for suspicious activity related to LinThesaurusCorpusReader and PanLexLiteCorpusReader constructors
• Implement compensating controls to restrict access to sensitive data and systems
• Verify and validate input data to prevent arbitrary corpus root paths

Evidence notes

Evidence from official sources indicates a path sandbox bypass vulnerability in NLTK versions before 3.10.3. The vulnerability allows attackers to read files outside the intended data root by supplying arbitrary corpus root paths to LinThesaurusCorpusReader and PanLexLiteCorpusReader constructors. Limited evidence suggests that this vulnerability may be exploited in the wild, but defenders should verify and validate input data to prevent arbitrary corpus root paths. Additional review of system logs and monitoring for suspicious activity related to LinThesaurusCorpusReader and PanLexLiteCorpusReader constructors is recommended.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.