CVE-2026-31048

Arbitrary code execution via malicious pickle payload in Pyro v3.x

Published Apr 13, 2026 CVSS 3.1 · 9.8 Critical EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

An attacker can supply a maliciously crafted pickled string to Pyro v3.x, which the library deserializes using Python’s pickle protocol without validation. Deserialization triggers execution of arbitrary code embedded in the payload, giving the attacker control over the target process and potentially compromising confidentiality, integrity, and availability. The vulnerability is a case of code injection through unsafe deserialization, classified as CWE‑94.

Affected Systems

Pyro v3.x is an RPC framework for Python. Any deployment of Pyro v3.x that accepts pickled messages from untrusted sources is affected. The vulnerability exists in the pickle protocol handling implemented in the Pyro library, and all releases of Pyro v3.x are at risk until an update is released.

Risk and Exploitability

The vulnerability carries a CVSS score of 9.8, indicating critical severity. The current EPSS score is <1%, reflecting a low but nonzero probability of exploitation. It is not listed in the CISA KEV catalog. The attack vector is remote and requires only that a malicious pickled payload be sent to a Pyro service. Based on the description, it is inferred that deserialization may occur before any authentication, which could make exploitation straightforward if the Pyro service is exposed.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Pyro to a patched release that removes or secures the unsafe pickle usage
  • Validate or reject pickled payloads before deserialization, or switch to a safer serialization format such as JSON or Protocol Buffers
  • Restrict external access to Pyro endpoints with firewalls or network segmentation to limit exposure to untrusted clients
  • Implement application‑level input validation to ensure only trusted sources can send pickled data

Generated by OpenCVE AI on April 17, 2026 at 08:58 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Title Arbitrary code execution via malicious pickle payload in Pyro v3.x
Type Values Removed Values Added
Title Arbitrary Code Execution via Pickle Deserialization in Pyro v3.x
Weaknesses CWE-502
Type Values Removed Values Added
Weaknesses CWE-94
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Title Arbitrary Code Execution via Pickle Deserialization in Pyro v3.x
Weaknesses CWE-502
Type Values Removed Values Added
First Time appeared Irmen
Irmen pyro3
Vendors & Products Irmen
Irmen pyro3
Type Values Removed Values Added
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.
References
Weaknesses
  • CWE-94

    Improper Control of Generation of Code ('Code Injection')

Sources

Status
PUBLISHED
Assigner
mitre
Published
Updated
Apr 15, 2026, 3:31 PM
Reserved
Mar 9, 2026, 12:00 AM
Status
Deferred
Published
Apr 13, 2026, 8:16 PM
Modified
Jun 17, 2026, 10:33 AM