PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-80205 nltk CVE debrief

The CVE-2026-80205 vulnerability affects NLTK versions before 3.10.0, specifically in the Text.findall() and TokenSearcher.findall() methods. These methods accept user-supplied regular expressions without validation or timeout, allowing attackers to supply crafted regex patterns that cause catastrophic backtracking. This results in indefinite CPU saturation and denial of service to all users of the Python process. The vulnerability has a HIGH CVSS score of 8.7, indicating a high severity. Users of NLTK versions before 3.10.0 should be aware of the potential denial of service vulnerability and take defensive actions. The CVE record was published on 2026-08-26T11:16:39.950Z and has not been modified since then.

Vendor
nltk
Product
Unknown
CVSS
HIGH 8.7
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-26
Original CVE updated
2026-09-03
Advisory published
2026-08-26
Advisory updated
2026-09-03

Who should care

Users of NLTK versions before 3.10.0, especially those using the Text.findall() and TokenSearcher.findall() methods, should be aware of the potential denial of service vulnerability and take defensive actions. This includes operators, platform administrators, vulnerability management teams, and security teams who need to assess and mitigate the risk associated with this vulnerability.

Technical summary

The CVE-2026-80205 vulnerability affects NLTK versions before 3.10.0, specifically the Text.findall() and TokenSearcher.findall() methods. These methods accept user-supplied regular expressions without validation or timeout, allowing attackers to supply crafted regex patterns that cause catastrophic backtracking. This results in indefinite CPU saturation and denial of service to all users of the Python process. The vulnerability has a HIGH CVSS score of 8.7, indicating a high severity. The NVD entry is currently Modified.

Defensive priority

High-priority defensive actions are required due to the HIGH CVSS score of 8.7 and the potential for denial of service attacks.

Recommended defensive actions

  • Inventory and assess NLTK usage in Python processes
  • Upgrade NLTK to version 3.10.0 or later
  • Implement compensating controls to monitor and limit resource usage
  • Review and restrict user-supplied regular expressions
  • Monitor for suspicious activity and exception tracking
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE-2026-80205 record indicates a regular expression denial of service vulnerability in NLTK versions before 3.10.0. The vulnerability affects the Text.findall() and TokenSearcher.findall() methods that accept user-supplied regular expressions without validation or timeout. Limited information is available on the scope of affected users and potential attack vectors.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-80205 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-80205

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-80205 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-80205

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://github.com/nltk/nltk/security/advisories/GHSA-rrv8-h7p8-rx55

    [email protected] - Exploit, Vendor Advisory

  • Source reference

    Unverified legacy reference

    URL: https://www.vulncheck.com/advisories/nltk-before-3.10.0-redos-via-text-findall-unvalidated-regex

    [email protected] - Third Party Advisory

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.