Local NLTK data tampering via shared cache
Published Oct 13, 2025 · Updated Oct 13, 2025
Insecure shared storage in LlamaIndex before 0.13.0 allows local users to corrupt NLTK data through a writable package cache. GlobalsHelper sets _nltk_data_dir to llama_index/core/_static/nltk_cache and trusts stopword and tokenizer data loaded from that shared path. Another account must be able to write the installed package tree; tampering can alter NLP processing or interrupt applications that import the library.
Summary
What happened
Insecure shared storage in LlamaIndex before 0.13.0 allows local users to corrupt NLTK data through a writable package cache. GlobalsHelper sets _nltk_data_dir to llama_index/core/_static/nltk_cache and trusts stopword and tokenizer data loaded from that shared path. Another account must be able to write the installed package tree; tampering can alter NLP processing or interrupt applications that import the library.
The record
- CVE
- CVE-2025-7707
- Published
- Oct 13, 2025
- Updated
- Oct 13, 2025
- Vendor
- LlamaIndex
- Product
- LlamaIndex
- Classifications
- CWE-377, T1565.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 13, 2025CVE publishedPublication date reported by the CVE source.
- Oct 13, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <v0.13.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Huntr bounty proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo