deepset-ai farm Tokenizer Loader tokenization.py EmbeddingTokenizer.from_pretrained path traversal
Affects deepset-ai FARM at commit 5919538 (0.8.1-snapshot) and release v0.8.0 when Tokenizer.load() is called on a local model directory whose name contains word2vec, glove or fasttext.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 22/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The deepset-ai FARM machine learning framework's tokenizer loading component is affected. A remote attacker who manipulates the vocabulary filename argument could use path traversal to reach files outside the intended directory, though the maintainer no longer supports this product.
Read the original description
A flaw has been found in deepset-ai farm up to 0.8.0. This impacts the function EmbeddingTokenizer.from_pretrained of the file farm/modeling/tokenization.py of the component Tokenizer Loader. Executing a manipulation of the argument vocab_filename can lead to path traversal. The attack may be performed from remote. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way. This vulnerability only affects products that are no longer supported by the maintainer.
What to do
Check whether your setup matches what the bug needs.
FARM at commit 5919538 (0.8.1-snapshot) and release v0.8.0 are affected The victim calls Tokenizer.load() on a local model package directory The model directory name contains word2vec, glove or fasttext, which makes FARM select EmbeddingTokenizer automaticallyWorkaround: The checked facts give no workaround. Limiting the affected feature means avoiding Tokenizer.load() on local model directories whose names contain word2vec, glove or fasttext while no fix is available.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- deepset-ai farm
0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8.0
Evidence 5
- Advisory
- Advisory
- Advisory
- Advisory
- Exploit
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120334
What does this mean?
Tokenizer.load() passes a local model directory to the embedding tokenizer, and a path inside it can point to files outside the package. The content of readable files outside the package can then be loaded into the tokenizer vocabulary, where it can be stored or sent elsewhere. Attacker-chosen vocabulary entries can also change the token-to-id mapping, and a file without an [UNK] line can crash the load.Source: github.com
Am I affected, and how do I check?
The checked facts list FARM at commit 5919538 (0.8.1-snapshot) and release v0.8.0. The setup involves calling Tokenizer.load() on a local model package directory whose name contains word2vec, glove or fasttext, which makes FARM select EmbeddingTokenizer automatically. To check a installation, compare its FARM version against those builds and review whether that call and directory naming pattern appear in the code.Source: github.com
What should I do about it?
The checked facts do not name a fixed version, so no upgrade target can be given. Check the vendor's advisory for a fix before relying on any release.Source: github.com
Is it 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. No public exploit code is tracked.Source: cve.now feed data
What if there's no patch?
The checked facts give no workaround. Limiting the affected feature means avoiding Tokenizer.load() on local model directories whose names contain word2vec, glove or fasttext while no fix is available.Source: github.com