Unauthenticated code execution via unsafe pickle deserialization
Published Apr 13, 2026 · Updated Apr 13, 2026
Unsafe deserialization in Pyro 3.16 and earlier allows remote attackers to execute arbitrary code through crafted network messages. During request handling, the protocol handler passes unauthenticated serialized message data to pickle.loads(), permitting attacker-selected object reconstruction and reduce callables. Any attacker able to reach a Pyro 3.x server can run code with the server process's privileges; no authentication or user interaction is required.
Summary
What happened
Unsafe deserialization in Pyro 3.16 and earlier allows remote attackers to execute arbitrary code through crafted network messages. During request handling, the protocol handler passes unauthenticated serialized message data to pickle.loads(), permitting attacker-selected object reconstruction and reduce callables. Any attacker able to reach a Pyro 3.x server can run code with the server process's privileges; no authentication or user interaction is required.
The record
- CVE
- CVE-2026-31048
- Published
- Apr 13, 2026
- Updated
- Apr 13, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-502, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 13, 2026CVE publishedPublication date reported by the CVE source.
- Apr 13, 2026Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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