Skip to main content
Menu
CVEs

NLTK schema injection in ARFF_Formatter

CVE-2026-129221EUVD-2026-130489Published November 19, 2026, updated

5.4MediumCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 3.10.4
Who is exposed
Not reported

Summary

NLTK, a Python toolkit for natural language processing, does not safely handle attacker-supplied class labels when writing Weka ARFF files, so crafted labels can change the generated file's schema or records. An attacker with low-level login access can trigger this remotely over the network, corrupting classifier input and causing integrity loss or processing failures.

Written by a model

Original description

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, nltk.classify.weka.ARFF_Formatter writes attacker-controlled class labels into the Weka ARFF @ATTRIBUTE '-label-' declaration without safely formatting the label tokens. Crafted labels can alter the generated ARFF schema or records, corrupting classifier input and causing integrity loss or processing failure. This issue is fixed in version 3.10.4.

What to do

Upgrade to a fixed version: 3.10.4.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129221 (NLTK: ARFF_Formatter Injects Weka ARFF Schema Directives via Attacker-Controlled Class Labels), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129221 (entry last updated 2026-11-19):
Affected:
- nltk nltk: fixed in 3.10.4
Fixed versions: 3.10.4.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129221 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129221 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/nltk/nltk/security/advisories/GHSA-9ffx-rrgx-mhgx
- https://github.com/nltk/nltk/pull/3768
- https://github.com/nltk/nltk/commit/56031eabc1ac6e5a109cb78bb18d10e0b7589594
- https://github.com/nltk/nltk/releases/tag/v3.10.4
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129221
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129221"}.

Affected versions

cve.now Index

23Pof 100 · provisional · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.4/10CVSS 5.4
  • No patch0/5No signal

What would change the score

  • Would score about 63 if added to CISA KEV
  • Would score about 58 if CISA's SSVC rates exploitation active
  • Would score about 42 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 6

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · nltk/nltk · Advisory GHSA-9ffx-rrgx-mhgx
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-129221
RecordNVD · CVE-2026-129221
Other links 3
RepositoryGitHub · nltk/nltk · Pull request #3768
RepositoryGitHub · nltk/nltk · Commit 56031eab
RepositoryGitHub · nltk/nltk · Release v3.10.4

Questions about CVE-2026-129221

Is CVE-2026-129221 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-129221?

nltk: before 3.10.4.

Source: cve.now feed data

How do I fix CVE-2026-129221?

Upgrade to a fixed version: 3.10.4.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.