Secuno
ENNL
Book demo

CVE-2025-7707

Llamaindex privilege escalation

7.8 HIGHPublic exploitEPSS 0.19%
  1. Published13 Oct 2025

Description

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 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.

CVSS 3.1 breakdown

Attack vectorLocal
Attack complexityLow
Privileges requiredLow
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

Llamaindex≥ 0.12.33 < 0.13.0

Remediation

Fixed in
Llamaindex≥ 0.13.0

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2025-143078.1
An insecure temporary file creation vulnerability exists in the AutoExtract component…
CVE-2015-52249.8
The mkostemp function in login-utils in util-linux when used incorrectly allows remote…

Frequently asked

Is CVE-2025-7707 being actively exploited?

CVE-2025-7707 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.19%.

How severe is CVE-2025-7707?

CVE-2025-7707 has a CVSS 3.1 base score of 7.8, rated high. EPSS estimates a 0.19% probability of exploitation.

Which products are affected by CVE-2025-7707?

Affected products include Llamaindex.

How do I fix CVE-2025-7707?

Upgrade affected software to a fixed version, for example Llamaindex 0.13.0 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-7707 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.