Remote code execution via unsafe pickle deserialization
Published Sep 25, 2025 · Updated Sep 25, 2025
Unsafe deserialization in vlarl at 31abc0baf53ef8f5db666a1c882e1ea64def2997 allows remote authenticated users to execute code via ZeroMQ messages. The run_reasoning_server function passes each received message directly to pickle.loads, so a crafted pickle invokes attacker-selected callables during deserialization. Network access to the ZeroMQ service and low privileges are required; successful exploitation runs code in the server process context.
Summary
What happened
Unsafe deserialization in vlarl at 31abc0baf53ef8f5db666a1c882e1ea64def2997 allows remote authenticated users to execute code via ZeroMQ messages. The run_reasoning_server function passes each received message directly to pickle.loads, so a crafted pickle invokes attacker-selected callables during deserialization. Network access to the ZeroMQ service and low privileges are required; successful exploitation runs code in the server process context.
The record
- CVE
- CVE-2025-10975
- Published
- Sep 25, 2025
- Updated
- Sep 25, 2025
- Vendor
- Guanxing Lu
- Product
- vlarl
- Classifications
- CWE-20, CWE-502, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 25, 2025CVE publishedPublication date reported by the CVE source.
- Sep 25, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=31abc0baf53ef8f5db666a1c882e1ea64def2997
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub issue 18 pickle payload proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo