PYSEC-2025-249

Vulnerability from pysec - Published: 2025-07-06 23:15 - Updated: 2026-07-13 05:49
VLAI
Details

A critical deserialization vulnerability exists in the run-llama/llama_index library's JsonPickleSerializer component, affecting versions v0.12.27 through v0.12.40. This vulnerability allows remote code execution due to an insecure fallback to Python's pickle module. JsonPickleSerializer prioritizes deserialization using pickle.loads(), which can execute arbitrary code when processing untrusted data. Attackers can exploit this by crafting malicious payloads to achieve full system compromise. The root cause includes an insecure fallback mechanism, lack of validation or safeguards, misleading design, and violation of Python security guidelines.

Severity
7.5 (High)
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Impacted products
Name purl
llama-index pkg:pypi/llama-index
Aliases
To clipboard 

{
  "affected": [
    {
      "ecosystem_specific": {},
      "package": {
        "ecosystem": "PyPI",
        "name": "llama-index",
        "purl": "pkg:pypi/llama-index"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.12.27"
            },
            {
              "fixed": "0.12.41"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "0.12.27",
        "0.12.28",
        "0.12.29",
        "0.12.30",
        "0.12.31",
        "0.12.32",
        "0.12.33",
        "0.12.34",
        "0.12.35",
        "0.12.36",
        "0.12.37",
        "0.12.38",
        "0.12.39",
        "0.12.40"
      ]
    }
  ],
  "aliases": [
    "CVE-2025-3108"
  ],
  "details": "A critical deserialization vulnerability exists in the run-llama/llama_index library\u0027s JsonPickleSerializer component, affecting versions v0.12.27 through v0.12.40. This vulnerability allows remote code execution due to an insecure fallback to Python\u0027s pickle module. JsonPickleSerializer prioritizes deserialization using pickle.loads(), which can execute arbitrary code when processing untrusted data. Attackers can exploit this by crafting malicious payloads to achieve full system compromise. The root cause includes an insecure fallback mechanism, lack of validation or safeguards, misleading design, and violation of Python security guidelines.",
  "id": "PYSEC-2025-249",
  "modified": "2026-07-13T05:49:40.746624Z",
  "published": "2025-07-06T23:15:21.777Z",
  "references": [
    {
      "type": "FIX",
      "url": "https://github.com/run-llama/llama_index/commit/702e4340623092fac4cf2fe95eb9465034856da3"
    },
    {
      "type": "EVIDENCE",
      "url": "https://huntr.com/bounties/9b55a5e8-74e6-4241-b323-e360dc8b110a"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.