CVE-2025-7707
Llamaindex 0.12.33 – 0.13.0
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2025-7707 is a high-severity Insecure Temporary File (CWE-377) vulnerability in Llamaindex Llamaindex. Its CVSS base score is 7.8 (High).
Operationally, ranked at the 7th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
This vulnerability is AI-related — categorised as NLP and Transformers; in the Data-Related Vulnerabilities risk domain.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-34071
Vulnerability Data
The llama_index library version 0.12.33 sets the NLTK data directory to a subdirectory of the codebase by default, which is world-writable in multi-user environments. This configuration allows local users to overwrite, delete, or corrupt NLTK data files, leading to potential…
more
denial of service, data tampering, or privilege escalation. The vulnerability arises from the use of a shared cache directory instead of a user-specific one, making it susceptible to local data tampering and denial of service.
- CWE(s)
AI Security AnalysisAI
- AI Category
- NLP and Transformers
- Risk Domain
- Data-Related Vulnerabilities
- OWASP Top 10 for LLMs 2025
- None mapped
- Classification Reason
- Matched keywords: nltk
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
AC-3 enforces file-system access authorizations so that temporary files cannot be read or modified by unauthorized processes.
AC-6 reduces the privileges available to processes that create or access temporary files, limiting blast radius if a file is predictable or left readable.
SC-4 directly stops unauthorized information leakage through shared resources such as world-writable temporary directories.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require avoiding insecure temp-file creation patterns.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect insecure temporary files but does not prevent their creation.
Secure development life cycle mandates secure handling of temporary files during design and coding.
Application security requirements can specify secure temporary-file creation and access controls.
Secure system architecture principles discourage insecure temporary-file patterns but do not directly address them.
Secure coding standards explicitly require safe temporary-file APIs and permissions.
Information deletion policies may cover secure removal of temporary files after use.