CVE-2026-31048 Details
Description
An issue in the <code>pickle</code> protocol of Pyro v3.x allows attackers to execute arbitrary code via supplying a crafted pickled string message.
A remote code execution vulnerability exists in Pyro versions 3.16 and prior, due to unsafe deserialization of untrusted data by the pickle protocol. When a crafted pickled string message is sent to a Pyro server, it is deserialized without any authentication or integrity checks, allowing attackers to execute arbitrary code on the server.
Users are advised to migrate to Pyro5, which does not use pickle for serialization by default and offers safer alternatives. If an immediate migration is not possible, Pyro3 should be used only over trusted networks and channels.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Apr 13, 2026CISA-ADP
Assessed Apr 15, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/irmen/Pyro3/blob/master/docs/9-security.html#L341-L346 | [email protected] | Technical DescriptionVendor |
| https://github.com/irmen/Pyro3/blob/master/Pyro/protocol.py#L672-L711 | [email protected] | Source CodeVendor |
| https://github.com/Sif-0x01/security-advisories/security/advisories/GHSA-7625-w9h5-83rv | [email protected] | AdvisoryRemedy |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-94 | Improper Control of Generation of Code ('Code Injection') | CISA-ADP |
Affected Products
| Product | Versions |
|---|---|
| irmen Pyro | <= 3.16 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Apr 15, 2026 | CVE Modified | CISA-ADP |
| Apr 13, 2026 | New CVE Received | [email protected] |
Volerion