CVE-2026-129228 json
NLTK: Uncontrolled recursion in Toolbox settings helpers causes denial of service via deeply nested input
published 6d ago modified yesterday also EUVD-2026-130496 , GHSA-f2h2-f4fc-p978
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 41%
- public exploits
- 0
- none known
Summary
NLTK (Natural Language Toolkit) is a suite of open source Python modules, data sets, and tutorials supporting research and development in Natural Language Processing. Prior to 3.10.4, ToolboxSettings.parse builds a deeply nested attacker-controlled settings tree iteratively, but the later public helpers to_settings_string, remove_blanks, add_default_fields, sort_fields, and add_blank_lines recursively traverse that tree without a depth bound. Invoking any of those helpers on input nested beyond the interpreter recursion limit can raise RecursionError and abort the operation or request worker. This issue is fixed in version 3.10.4.
Patch / fix
- pypi nltk 3.10.4
- github.com/nltk/nltk@0b69753 commit
- github.com/nltk/nltk#3885 pull request
- github.com/nltk/nltk/releases/tag/v3.10.4 release
Is CVE-2026-129228 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-129228 updated cvss 5.3
nltk: nltk: Denial of Service via unbounded recursion in ToolboxSettings
-
Red Hat Lightspeed Core lightspeed-core/rag-tool-cpu-rhel9, lightspeed-core/lightspeed-stack-rhel9, lightspeed-core/rag-tool-cuda-12.9-rhel9 Red Hat OpenShift Lightspeed openshift-lightspeed/lightspeed-ocp-rag-rhel9, openshift-lightspeed/lightspeed-service-api-rhel9, openshift-lightspeed-tech-preview/lightspeed-rag-tool-rhel9 Red Hat Ansible Automation Platform 2 ansible-automation-platform-25/lightspeed-chatbot-rhel8 Red Hat OpenShift AI (RHOAI) rhoai/odh-ogx-core-rhel9, rhoai/odh-ta-lmes-job-rhel9, rhoai/odh-llama-stack-core-rhel9, rhoai/odh-trustyai-garak-lls-provider-dsp-rhel9, rhoai/odh-trustyai-nemo-guardrails-server-rhel9, rhoai/odh-pipeline-runtime-pytorch-llmcompressor-cuda-py312-rhel9, +1 moreaffected: workaround, no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- yesterday
Exploit prediction
0.47% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-21).
Exploits and checks
- github.com https://github.com/nltk/nltk/security/advisories/GHSA-f2h2-f4fc-p978 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | nltk | <3.10.4 |
3.10.4 |
Affected products
- nltk nltk
Classification
- Weakness
-
- CWE-674 Uncontrolled Recursion
References
-
github.com
/nltk/nltk/pull/3885
web
-
github.com
/nltk/nltk/commit/0b6975377d0334af604d32c9d83b26b46e1d437c
web
-
github.com
/nltk/nltk/security/advisories/GHSA-f2h2-f4fc-p978
exploit, web, advisory
-
github.com
/nltk/nltk/releases/tag/v3.10.4
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-129228
advisory
-
github.com
/nltk/nltk
package
Sources
- CVE List CVE-2026-129228
- GitHub Advisory GHSA-f2h2-f4fc-p978
- NVD CVE-2026-129228
- Maintainer advisory GHSA-f2h2-f4fc-p978
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of nltk/nltk published their own advisory on GitHub. Reviewed sources take precedence over it.