nltk PorterStemmer in versions <= 3.10.2 (fixed in 3.10.3) contains an inefficient-algorithmic-complexity denial of service in PorterStemmer.stem(). The _is_consonant() helper walks backward over the entire run of trailing 'y' characters on every call, and _measure() invokes it for each stem position, causing O(n^2) behavior. A single ~20-50 KB untrusted token consisting of a long run of the letter 'y' followed by a matching suffix (e.g., 'ness') can pin a CPU core for seconds to minutes, causing availability impact.
CVE-2026-81722
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-27. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 38(Track)EG Risk 38/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 30%
- KEV
- Not listed
Published
August 27, 2026
Last Modified
August 31, 2026
Advisory Details (2)
Auto-updated Aug 27, 2026nltk PorterStemmer before 3.10.3 Quadratic-time DoS | Advisories | VulnCheck
https://www.vulncheck.com/advisories/nltk-porterstemmer-before-3.10.3-quadratic-time-dosQuadratic-time DoS in PorterStemmer via long runs of 'y' · Advisory · nltk/nltk · GitHub
https://github.com/nltk/nltk/security/advisories/GHSA-ww6m-cw3f-q94gVendor Advisories for CVE-2026-81722(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(4 across 4 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nltk | 3.10.0-1 ... 3.9.3-1 (9 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nltk | 3.10.0-1 ... 3.9.3-1 (6 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nltk | 3.10.0-1, 3.10.1-1, 3.9.1-2, 3.9.2-1, 3.9.3-1 | 3.10.3-1 | — |
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nltk | 0.8 ... 3.9b1 (68 versions) | 3.10.3 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 55× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-19 00:59 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 00:03 UTCEG score recompute
- 2026-09-16 21:44 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 09:15 UTCEG score recompute
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 07:17 UTCEG score recompute
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-13 17:04 UTCEG score recompute
- 2026-09-12 16:06 UTCEG score recompute
- 2026-09-11 15:10 UTCEG score recompute
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 14:11 UTCEG score recompute
- 2026-09-09 00:40 UTCEG score recompute
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-08 03:35 UTCEG score recompute
- 2026-09-07 01:27 UTCEG score recompute
- 2026-09-06 13:48 UTCEPSS rescore
- 2026-09-06 00:31 UTCEG score recompute
- 2026-09-05 15:31 UTCEPSS rescore
- 2026-09-04 23:32 UTCEG score recompute
- 2026-09-04 09:58 UTCEG score recompute
Show 30 moreShow fewer
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-02 20:29 UTCEG score recompute
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-02 05:39 UTCGHSA enrichment
- 2026-09-01 17:07 UTCEG score recompute
- 2026-09-01 17:06 UTCGHSA enrichment
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-09-01 04:32 UTCGHSA enrichment
- 2026-08-31 16:01 UTCGHSA enrichment
- 2026-08-31 09:32 UTCGHSA enrichment
- 2026-08-30 21:03 UTCEG score recompute
- 2026-08-30 21:03 UTCGHSA enrichment
- 2026-08-30 19:18 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 08:35 UTCEG score recompute
- 2026-08-30 08:35 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 20:06 UTCGHSA enrichment
- 2026-08-29 07:34 UTCEG score recompute
- 2026-08-29 07:34 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 19:03 UTCGHSA enrichment
- 2026-08-28 08:59 UTCGHSA enrichment
- 2026-08-27 20:27 UTCEG score recompute
- 2026-08-27 20:27 UTCGHSA enrichment
- 2026-08-27 17:24 UTCEG score recompute
- 2026-08-27 16:47 UTCEG score recompute
- 2026-08-27 16:43 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-81722?
When was CVE-2026-81722 disclosed?
Is CVE-2026-81722 actively exploited?
What is the CVSS score of CVE-2026-81722?
How do I remediate CVE-2026-81722?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-81722
Is Your Infrastructure Affected by CVE-2026-81722?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.