CVE-2026-80206
A permanent, source-backed tracker page. Values are shown only when returned; explicit gaps and read failures remain different states.
Detection and validation
Mapped metadata availability only. These signals do not change priority.
Sigma
Not mapped by tracked sources.
Atomic
Not mapped by tracked sources.
Nuclei
Not mapped by tracked sources.
What it is
ReportedNLTK before 3.10.3 contains a regular expression denial of service (ReDoS) vulnerability in the tgrep module. The _tgrep_node_action function compiles user-supplied regular expressions embedded in /regex/ pattern nodes and executes them via re.search against tree node labels without any validation or timeout. An attacker who controls the tgrep pattern (e.g., via tgrep_positions() or tgrep_compile() exposed to external input) can supply a pattern that triggers catastrophic backtracking, causing indefinite CPU saturation that blocks the Python process. Source description excerpt; complete tracked detail loads below.
Source reported · Source: NVD · Source last published: · Source last updated: · Tracker data as of:
What is affected
Reportednltk; NLTK. Product-level identification only; no affected-version conclusion is available from this field.
Source reported · Source: NVD · Source last published: · Source last updated: · Tracker data as of:
Urgency and basis
ReportedTrack* · 224.1
Tracker computed · Tracker decision tier from the evidence detailed below · Source last updated: · Tracker data as of:
Exploitation evidence
Not reportedNot reported by tracked sources.
What to do
ReportedA source remediation link is available. Validate that guidance against the affected product and your environment.
Source remediation ↗Source reported · Tracked source remediation field · Source last updated: · Tracker data as of:
Evidence detail
Loading the full tracker evidence record…