CVE-2026-31220

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.2%CVSS: 9.8Exploit: None knownExposed services: Not assessed

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

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.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/100

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 (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation1.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
1.2%
EPSS %ILE
67th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 12, 2026

Last Modified

May 15, 2026

Advisory Details (2)

Auto-updated Oct 8, 2026
No fix on record yet.
Web page

Notion

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

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 / EcosystemFix (by version range) / 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 rangeFix by version rangeDependents
syft0.1.0a1 ... 0.9.5 (320 versions)
  • every version through 0.9.5: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 35× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 363 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 268 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-16 16:41 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  2. 2026-10-16 14:34 UTCEG score recompute
  3. 2026-10-16 14:34 UTCGHSA enrichmentGHSA-cfpg-c974-jfhq · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-10-15 16:31 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  5. 2026-10-15 15:17 UTCEG score recompute
  6. 2026-10-15 15:17 UTCGHSA enrichmentGHSA-cfpg-c974-jfhq · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-14 16:32 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  8. 2026-10-14 09:43 UTCEG score recompute
  9. 2026-10-14 09:43 UTCGHSA enrichmentGHSA-cfpg-c974-jfhq · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-13 16:34 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  11. 2026-10-13 07:29 UTCEG score recompute
  12. 2026-10-13 07:28 UTCGHSA enrichmentGHSA-cfpg-c974-jfhq · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-12 16:34 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  14. 2026-10-12 16:15 UTCEG score recompute
  15. 2026-10-12 08:38 UTCGHSA enrichmentGHSA-cfpg-c974-jfhq · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-11 19:57 UTCEG score recompute
  17. 2026-10-11 17:11 UTCEG score recompute
  18. 2026-10-11 14:39 UTCEG score recompute
  19. 2026-10-11 13:48 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  20. 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  21. 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  22. 2026-10-08 17:12 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  23. 2026-10-07 23:47 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  24. 2026-10-06 15:17 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  25. 2026-10-05 17:42 UTCEPSS rescoreEPSS 1.2% · 67th percentile
Show 70 more
  1. 2026-10-04 23:22 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  2. 2026-10-03 14:25 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  3. 2026-10-01 19:49 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  4. 2026-09-30 15:03 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  5. 2026-09-28 13:51 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  6. 2026-09-26 15:58 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  7. 2026-09-26 00:26 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  8. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  9. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  10. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  11. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  12. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  13. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  14. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  15. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  16. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  17. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  18. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  19. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  20. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  21. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  22. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  23. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  24. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  25. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  26. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  27. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  28. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  29. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  30. 2026-08-24 14:17 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  31. 2026-08-23 18:25 UTCEG score recompute
  32. 2026-08-23 18:25 UTCGHSA enrichmentGHSA-cfpg-c974-jfhq · GitHub severity CRITICAL · GitHub CVSS 9.8
  33. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  34. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  35. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  36. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  37. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  38. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  39. 2026-08-17 10:55 UTCEG score recompute
  40. 2026-08-17 10:55 UTCGHSA enrichmentGHSA-cfpg-c974-jfhq · GitHub severity CRITICAL · GitHub CVSS 9.8
  41. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  42. 2026-08-16 12:33 UTCGHSA enrichmentGHSA-cfpg-c974-jfhq · GitHub severity CRITICAL · GitHub CVSS 9.8
  43. 2026-08-16 08:25 UTCGHSA enrichmentGHSA-cfpg-c974-jfhq · GitHub severity CRITICAL · GitHub CVSS 9.8
  44. 2026-08-16 04:17 UTCEG score recompute
  45. 2026-08-16 04:17 UTCGHSA enrichmentGHSA-cfpg-c974-jfhq · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  47. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  48. 2026-08-14 23:31 UTCGHSA enrichmentGHSA-cfpg-c974-jfhq · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-08-14 19:24 UTCGHSA enrichmentGHSA-cfpg-c974-jfhq · GitHub severity CRITICAL · GitHub CVSS 9.8
  50. 2026-08-14 15:11 UTCGHSA enrichmentGHSA-cfpg-c974-jfhq · GitHub severity CRITICAL · GitHub CVSS 9.8
  51. 2026-08-14 11:03 UTCGHSA enrichmentGHSA-cfpg-c974-jfhq · GitHub severity CRITICAL · GitHub CVSS 9.8
  52. 2026-08-14 06:56 UTCGHSA enrichmentGHSA-cfpg-c974-jfhq · GitHub severity CRITICAL · GitHub CVSS 9.8
  53. 2026-08-14 02:48 UTCEG score recompute
  54. 2026-08-14 02:48 UTCGHSA enrichmentGHSA-cfpg-c974-jfhq · GitHub severity CRITICAL · GitHub CVSS 9.8
  55. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  56. 2026-08-13 08:48 UTCGHSA enrichmentGHSA-cfpg-c974-jfhq · GitHub severity CRITICAL · GitHub CVSS 9.8
  57. 2026-08-13 04:40 UTCGHSA enrichmentGHSA-cfpg-c974-jfhq · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-08-13 00:32 UTCGHSA enrichmentGHSA-cfpg-c974-jfhq · GitHub severity CRITICAL · GitHub CVSS 9.8
  59. 2026-08-12 20:25 UTCGHSA enrichmentGHSA-cfpg-c974-jfhq · GitHub severity CRITICAL · GitHub CVSS 9.8
  60. 2026-08-12 16:17 UTCEG score recompute
  61. 2026-08-12 16:17 UTCGHSA enrichmentGHSA-cfpg-c974-jfhq · GitHub severity CRITICAL · GitHub CVSS 9.8
  62. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  63. 2026-08-11 23:59 UTCGHSA enrichmentGHSA-cfpg-c974-jfhq · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-08-11 19:51 UTCGHSA enrichmentGHSA-cfpg-c974-jfhq · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-08-11 15:43 UTCEG score recompute
  66. 2026-08-11 15:43 UTCGHSA enrichmentGHSA-cfpg-c974-jfhq · GitHub severity CRITICAL · GitHub CVSS 9.8
  67. 2026-08-11 09:20 UTCGHSA enrichmentGHSA-cfpg-c974-jfhq · GitHub severity CRITICAL · GitHub CVSS 9.8
  68. 2026-08-11 05:12 UTCGHSA enrichmentGHSA-cfpg-c974-jfhq · GitHub severity CRITICAL · GitHub CVSS 9.8
  69. 2026-08-11 01:05 UTCEG score recompute
  70. 2026-08-11 01:05 UTCGHSA enrichmentGHSA-cfpg-c974-jfhq · GitHub severity CRITICAL · GitHub CVSS 9.8

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-31220?
CVE-2026-31220 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-31220 published?
The CVE record for CVE-2026-31220 was published on May 12, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of May 15, 2026; the record at its source may have been updated since.
Is CVE-2026-31220 actively exploited?
CVE-2026-31220 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% probability of exploitation in the next 30 days (67th percentile of EPSS-scored CVEs).
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?
No fix for CVE-2026-31220 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-31220 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs