Skip to main content

PySyft CVE-2026-31220

| EUVD-2026-29504 CRITICAL
Code Injection (CWE-94)
2026-05-12 mitre GHSA-cfpg-c974-jfhq
9.8
CVSS 3.1
Share

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

3
Analysis Generated
May 15, 2026 - 21:30 vuln.today
CVSS changed
May 15, 2026 - 19:22 NVD
9.8 (CRITICAL)
CVE Published
May 12, 2026 - 00:00 nvd
UNKNOWN (no severity yet)

Blast Radius

ecosystem impact
† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth
  • 1 pypi packages depend on syft (1 direct, 0 indirect)

Ecosystem-wide dependent count for version 0.9.5.

DescriptionNVD

PySyft (Syft Datasite/Server) versions 0.9.5 and earlier are vulnerable to remote code execution due to insufficient validation and sandboxing of user-submitted code. The system allows low-privileged users to submit Python functions (via @sy.syft_function()) for remote execution on the server. While a code approval mechanism exists, the submitted code undergoes no security checks for dangerous operations (e.g., file access, command execution). Once approved, the code is executed within the server process using exec() and eval() functions without proper isolation. A remote attacker can leverage this to execute arbitrary Python code on the server, leading to complete compromise of the server environment.

AnalysisAI

Remote code execution in PySyft Datasite/Server versions 0.9.5 and earlier allows unauthenticated attackers to execute arbitrary Python code on the server through the function submission mechanism. The vulnerability stems from insufficient validation and sandboxing of user-submitted Python functions decorated with @sy.syft_function(), which are executed using unsafe exec() and eval() calls after approval. …

Sign in for full analysis, threat intelligence, and remediation guidance.

RemediationAI

Within 24 hours: Identify all systems running PySyft Datasite/Server versions 0.9.5 or earlier and isolate them from production networks or disable remote function submission capabilities. Within 7 days: Implement network-level controls restricting access to PySyft instances to trusted internal networks only, and monitor for suspicious function submissions or Python code patterns. …

Sign in for detailed remediation steps.

Share

CVE-2026-31220 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy