CVE-2026-31220

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-12. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
59(Track)
EG Risk 59/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
46.5%
KEV
Not listed

Published

May 12, 2026

Last Modified

May 15, 2026

Advisory Details (2)

Auto-updated Jun 21, 2026
No patch confirmed yet.
generic

Notion

https://www.notion.so/CVE-2026-31220-35d1e1393188814186b9e00114a8aba7
generic

GitHub - OpenMined/PySyft: Perform data science on data that remains in someone else's server · GitHub

https://github.com/OpenMined/PySyft

Vendor Advisories for CVE-2026-31220(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
pipsyft—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
syft0.1.0a1 ... 0.9.5 (320 versions)——

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 54× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 209 total refreshes for this CVE.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:08 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-22 14:08 UTCEPSS rescore
  6. 2026-07-21 15:24 UTCEPSS rescore
  7. 2026-07-21 15:24 UTCEPSS rescore
  8. 2026-07-20 17:08 UTCEPSS rescore
  9. 2026-07-20 17:08 UTCEPSS rescore
  10. 2026-07-19 14:31 UTCEPSS rescore
  11. 2026-07-19 14:31 UTCEPSS rescore
  12. 2026-07-19 02:29 UTCEPSS rescore
  13. 2026-07-18 10:04 UTCEPSS rescore
  14. 2026-07-18 10:04 UTCEPSS rescore
  15. 2026-07-16 17:03 UTCEPSS rescore
  16. 2026-07-16 17:03 UTCEPSS rescore
  17. 2026-07-15 16:57 UTCEPSS rescore
  18. 2026-07-15 16:57 UTCEPSS rescore
  19. 2026-07-15 02:00 UTCEPSS rescore
  20. 2026-07-15 02:00 UTCEPSS rescore
  21. 2026-07-13 22:30 UTCEPSS rescore
  22. 2026-07-13 06:13 UTCEPSS rescore
  23. 2026-07-13 06:13 UTCEPSS rescore
  24. 2026-07-12 05:46 UTCEPSS rescore
  25. 2026-07-11 08:27 UTCEPSS rescore
Show 75 more
  1. 2026-07-09 19:10 UTCEPSS rescore
  2. 2026-07-08 15:15 UTCEPSS rescore
  3. 2026-07-07 13:46 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 06:31 UTCEPSS rescore
  10. 2026-07-01 15:06 UTCEPSS rescore
  11. 2026-06-30 23:22 UTCEPSS rescore
  12. 2026-06-29 14:06 UTCEPSS rescore
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-28 14:07 UTCEPSS rescore
  15. 2026-06-28 14:07 UTCEPSS rescore
  16. 2026-06-28 13:28 UTCGHSA enrichment
  17. 2026-06-28 08:24 UTCGHSA enrichment
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-28 04:56 UTCEPSS rescore
  20. 2026-06-28 02:21 UTCGHSA enrichment
  21. 2026-06-27 13:18 UTCGHSA enrichment
  22. 2026-06-27 08:25 UTCGHSA enrichment
  23. 2026-06-27 03:08 UTCEPSS rescore
  24. 2026-06-26 20:55 UTCGHSA enrichment
  25. 2026-06-26 04:02 UTCGHSA enrichment
  26. 2026-06-25 23:25 UTCGHSA enrichment
  27. 2026-06-25 13:49 UTCEPSS rescore
  28. 2026-06-25 13:49 UTCEPSS rescore
  29. 2026-06-24 14:05 UTCEPSS rescore
  30. 2026-06-23 21:33 UTCEPSS rescore
  31. 2026-06-23 21:33 UTCEPSS rescore
  32. 2026-06-22 14:25 UTCEPSS rescore
  33. 2026-06-22 14:25 UTCEPSS rescore
  34. 2026-06-21 14:56 UTCEPSS rescore
  35. 2026-06-21 14:56 UTCEPSS rescore
  36. 2026-06-21 01:59 UTCEPSS rescore
  37. 2026-06-19 19:25 UTCEPSS rescore
  38. 2026-06-19 19:25 UTCEPSS rescore
  39. 2026-06-18 17:52 UTCEPSS rescore
  40. 2026-06-18 17:52 UTCEPSS rescore
  41. 2026-06-17 17:53 UTCEPSS rescore
  42. 2026-06-17 05:14 UTCGHSA enrichment
  43. 2026-06-17 00:23 UTCGHSA enrichment
  44. 2026-06-16 17:52 UTCEPSS rescore
  45. 2026-06-16 11:45 UTCGHSA enrichment
  46. 2026-06-16 06:43 UTCGHSA enrichment
  47. 2026-06-15 17:49 UTCEPSS rescore
  48. 2026-06-15 07:59 UTCGHSA enrichment
  49. 2026-06-15 03:16 UTCGHSA enrichment
  50. 2026-06-14 23:18 UTCEPSS rescore
  51. 2026-06-14 23:07 UTCGHSA enrichment
  52. 2026-06-14 18:58 UTCGHSA enrichment
  53. 2026-06-14 14:50 UTCGHSA enrichment
  54. 2026-06-14 10:42 UTCGHSA enrichment
  55. 2026-06-14 06:35 UTCGHSA enrichment
  56. 2026-06-14 00:58 UTCGHSA enrichment
  57. 2026-06-13 23:00 UTCEPSS rescore
  58. 2026-06-13 06:55 UTCGHSA enrichment
  59. 2026-06-13 02:19 UTCGHSA enrichment
  60. 2026-06-12 23:12 UTCEPSS rescore
  61. 2026-06-12 23:12 UTCEPSS rescore
  62. 2026-06-12 22:06 UTCGHSA enrichment
  63. 2026-06-12 17:57 UTCGHSA enrichment
  64. 2026-06-12 13:49 UTCGHSA enrichment
  65. 2026-06-12 09:28 UTCGHSA enrichment
  66. 2026-06-12 05:21 UTCGHSA enrichment
  67. 2026-06-12 01:13 UTCGHSA enrichment
  68. 2026-06-11 21:05 UTCGHSA enrichment
  69. 2026-06-11 16:57 UTCGHSA enrichment
  70. 2026-06-11 14:00 UTCEPSS rescore
  71. 2026-06-11 11:40 UTCGHSA enrichment
  72. 2026-06-11 07:31 UTCGHSA enrichment
  73. 2026-06-11 03:23 UTCGHSA enrichment
  74. 2026-06-10 23:15 UTCGHSA enrichment
  75. 2026-06-10 22:18 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-31220?
CVE-2026-31220 is a critical vulnerability published on May 12, 2026. 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.…
When was CVE-2026-31220 disclosed?
CVE-2026-31220 was first published in the National Vulnerability Database on May 12, 2026, with the most recent update on May 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31220 actively exploited?
CVE-2026-31220 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 46.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31220?
CVE-2026-31220 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-31220?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31220, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31220

Explore →

Is Your Infrastructure Affected by CVE-2026-31220?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs