# LlamaIndex vulnerable to Creation of Temporary File in Directory with Insecure Permissions

Advisory record · `GHSA-jmgm-gx32-vp4w`

- **Identifiers:** `GHSA-jmgm-gx32-vp4w` · `CVE-2024-12911` · `PYSEC-2026-1555`
- **State:** Confirmed
- **Severity:** CVSS 7.1 High
- **Critical:** No
- **Weakness (CWE):** [CWE-89](https://cwe.mitre.org/data/definitions/89.html) · [CWE-379](https://cwe.mitre.org/data/definitions/379.html)
- **Tags:** [SQL injection](https://agentprime.io/advisories/tag/sql-injection.md) · [CWE-379](https://agentprime.io/advisories/tag/cwe-379.md)
- **Published:** 20 Mar 2025
- **Updated:** 7 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 20 Mar 2025, 12:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `llama-index` (PyPI): affected `<0.12.3`; fixed in `0.12.3`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.1 High, CVSS 3.0: `CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H`, from CNA (@huntr_ai)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0052, the 44th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 20 Mar 2025. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-jmgm-gx32-vp4w](https://github.com/advisories/GHSA-jmgm-gx32-vp4w)
- [OSV: GHSA-jmgm-gx32-vp4w](https://osv.dev/vulnerability/GHSA-jmgm-gx32-vp4w)
- <https://nvd.nist.gov/vuln/detail/CVE-2024-12911>
- <https://github.com/run-llama/llama_index/commit/bf282074e20e7dafd5e2066137dcd4cd17c3fb9e>
- <https://github.com/run-llama/llama_index>
- <https://huntr.com/bounties/095f9e67-311d-494c-99c5-5e61a0adb8f3>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-jmgm-gx32-vp4w>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-jmgm-gx32-vp4w/>. Everything for agents: <https://agentprime.io/llms.txt>.
