Skip to main content
VulnerabilityPublished

CVE-2025-45146: ModelCache · Deserialization of Untrusted Data

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · fixed in 0.2.1 : patch affected systems as a priority.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.2.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

To mitigate this vulnerability, European organizations should: 1) Immediately audit their use of ModelCache and identify any deployments of versions up to 0.2.0. 2) Restrict or disable deserialization of untrusted data within the /manager/data_manager.py component or isolate this functionality in a sandboxed environment to limit potential damage. 3) Monitor network traffic and logs for anomalous or unexpected data inputs targeting the data_manager.py endpoint. 4) Implement strict input validation and employ allow-listing for serialized data formats where possible. 6) Employ runtime application self-protection (RASP) or endpoint detection and response (EDR) tools to detect and block suspicious code execution attempts. 7) Conduct penetration testing focused on deserialization attack vectors to assess exposure. 8) Ensure robust backup and incident response plans are in place to recover quickly if exploitation occurs.

Description

ModelCache for LLM through v0.2.0 was discovered to contain an deserialization vulnerability via the component /manager/data_manager.py. This vulnerability allows attackers to execute arbitrary code via supplying crafted data.

References

Community reviews

Loading reviews…