Skops may allow MethodNode to access unexpected object fields through dot notation, leading to arbitrary code execution at load time
CVE-2025-54413 · GHSA-4v6w-xpmh-gfgp · published 2025-07-25 · updated 2025-09-05
- Severity
- High
- CVSS score
- 8.7
- Chance of exploitation (EPSS)
- 0.16%
- Fixed in
- 0.12.0
- Exploitation Public proof of concept
- Automatable No
- Technical impact Total
- CISA SSVC
An attacker can craft a malicious model file that, when loaded, executes arbitrary code on the victim’s machine. This occurs at load time, requiring no user interaction beyond loading the model. Given that skops is often used in collaborative environments and is designed with security in mind, this vulnerability poses a significant threat.
Upgrade skops to 0.12.0 or later.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| skops | PyPI | < 0.12.0 | 0.12.0 |
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.