CVE-2026-57516

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-24. The CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Elevated

Also known asEUVD-2026-41089 (ENISA EUVD) · GHSA-hhrp-gw25-jr43 (GitHub Security Advisories) · PYSEC-2026-2273 (OSV.dev)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.1%CVSS: 8.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Ray prior to 2.56.0 contains an unsafe deserialization vulnerability in the WebDataset reader that allows attackers to achieve remote code execution by supplying a malicious tar archive to the read_webdataset() function. The _default_decoder() function in webdataset_datasource.py unconditionally calls pickle.loads() on tar entries with .pkl/.pickle extensions and torch.load() with weights_only=False on .pt/.pth entries, executing arbitrary code inside Ray remote workers on every worker that processes the malicious archive.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
56
EG Risk 56/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.1%
EPSS %ILE
65th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.1% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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

July 1, 2026

Last Modified

November 8, 2026

Advisory Details (5)

Auto-updated Jul 1, 2026
Patch available. Sources: github_release, github, github_pr.
GitHub advisoryMentions a patch (unverified)

Arbitrary code execution via ray.data.read_webdataset default decoder: pickle.loads(value) and torch.load(weights_only=False) · Advisory · ray-project/ray · GitHub

Affected: 2.55.0): standard

https://github.com/ray-project/ray/security/advisories/GHSA-hhrp-gw25-jr43
Web page

Ray < 2.56.0 Unsafe Deserialization RCE via WebDataset Reader | Advisories | VulnCheck

https://www.vulncheck.com/advisories/ray-unsafe-deserialization-rce-via-webdataset-reader
GitHub release Patch Available

Ray-2.56.0

Patch available: ray-project/ray ray-2.56.0

https://github.com/ray-project/ray/releases/tag/ray-2.56.0
GitHub pull request

[Data] Block pickle object columns when reading untrusted Parquet files

Fix merged in ray-project/ray PR #63470 on 2026-05-19 — awaiting tagged release

https://github.com/ray-project/ray/pull/63470
GitHub pull request

[Data] Gate unsafe deserialization in WebDataset default decoder

Fix merged in ray-project/ray PR #63469 on 2026-05-19 — awaiting tagged release

https://github.com/ray-project/ray/pull/63469

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17927211922026-10-29redhat
redhatrhelai3/bootc-gcp-cuda-rhel9:17909363342026-10-05redhat
redhatrhelai3/disk-image-cuda-rhel9:17909541792026-10-05redhat
redhatrhaiis/vllm-cuda-rhel9:17895827762026-09-17redhat
redhatrhaiis/vllm-cuda-rhel9:17878605802026-08-31redhat
pipray @ 2.56.0 (fixes < 2.56.0)—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
ray0.1.1 ... 2.9.3 (128 versions)
  • every version up to 2.56.0: fixed in 2.56.0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 39× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 217 rows 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. None are among the latest 100 rows. The 117 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:53 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  2. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  3. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  4. 2026-11-10 16:44 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  5. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  6. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  7. 2026-11-08 14:18 UTCEchelonGraph re-scored
  8. 2026-11-08 14:18 UTCVendor advisory
  9. 2026-11-08 14:18 UTCGHSA enrichmentGHSA-hhrp-gw25-jr43 · GitHub severity HIGH · GitHub CVSS 8.8
  10. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  11. 2026-11-06 16:38 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  12. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  13. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  14. 2026-11-04 13:38 UTCEchelonGraph re-scored
  15. 2026-11-04 13:38 UTCVendor advisory
  16. 2026-11-04 13:38 UTCGHSA enrichmentGHSA-hhrp-gw25-jr43 · GitHub severity HIGH · GitHub CVSS 8.8
  17. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  18. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  19. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  20. 2026-11-01 07:42 UTCGHSA enrichmentGHSA-hhrp-gw25-jr43 · GitHub severity HIGH · GitHub CVSS 8.8
  21. 2026-11-01 07:42 UTCEchelonGraph re-scored
  22. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  23. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  24. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  25. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
Show 75 more
  1. 2026-10-27 21:03 UTCEchelonGraph re-scored
  2. 2026-10-27 21:03 UTCVendor advisory
  3. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  4. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  5. 2026-10-25 17:32 UTCEchelonGraph re-scored
  6. 2026-10-25 17:32 UTCVendor advisory
  7. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  8. 2026-10-25 14:17 UTCEchelonGraph re-scored
  9. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  10. 2026-10-24 07:50 UTCEchelonGraph re-scored
  11. 2026-10-24 07:50 UTCVendor advisory
  12. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  13. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  14. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  15. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  16. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  17. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  18. 2026-10-18 03:28 UTCEchelonGraph re-scored
  19. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  20. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  21. 2026-10-16 15:12 UTCEchelonGraph re-scored
  22. 2026-10-16 15:12 UTCVendor advisory
  23. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  24. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  25. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  26. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  27. 2026-10-12 15:54 UTCEchelonGraph re-scored
  28. 2026-10-11 19:37 UTCEchelonGraph re-scored
  29. 2026-10-11 16:52 UTCEchelonGraph re-scored
  30. 2026-10-11 14:15 UTCEchelonGraph re-scored
  31. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  32. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  33. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  34. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  35. 2026-10-08 16:40 UTCEchelonGraph re-scored
  36. 2026-10-08 16:40 UTCVendor advisory
  37. 2026-10-08 15:46 UTCEchelonGraph re-scored
  38. 2026-10-08 15:46 UTCVendor advisory
  39. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  40. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  41. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  42. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  43. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  44. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  45. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  46. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  47. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  48. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  49. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  50. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  51. 2026-09-24 15:01 UTCEchelonGraph re-scored
  52. 2026-09-24 15:01 UTCVendor advisory
  53. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  54. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  55. 2026-09-23 06:52 UTCEchelonGraph re-scored
  56. 2026-09-23 06:52 UTCVendor advisory
  57. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  58. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  59. 2026-09-18 06:33 UTCEchelonGraph re-scored
  60. 2026-09-18 06:33 UTCVendor advisory
  61. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  62. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  63. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  64. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  65. 2026-09-14 00:23 UTCEchelonGraph re-scored
  66. 2026-09-14 00:23 UTCVendor advisory
  67. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  68. 2026-09-13 09:08 UTCEchelonGraph re-scored
  69. 2026-09-13 09:08 UTCVendor advisory
  70. 2026-09-12 14:42 UTCEchelonGraph re-scored
  71. 2026-09-12 14:42 UTCVendor advisory
  72. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  73. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  74. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  75. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.9% · 56th percentile

Frequently asked(5)

What is CVE-2026-57516?
CVE-2026-57516 is a high-severity vulnerability; its CVE record was published on July 1, 2026. Ray prior to 2.56.0 contains an unsafe deserialization vulnerability in the WebDataset reader that allows attackers to achieve remote code execution by supplying a malicious tar archive to the read_webdataset() function. The _default_decoder() function in webdataset_datasource.py unconditionally…
When was CVE-2026-57516 made public?
CVE-2026-57516 was made public on May 18, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 1, 2026. EchelonGraph's copy of the record carries a last-modified date of November 8, 2026; the record at its source may have been updated since.
Is CVE-2026-57516 actively exploited?
CVE-2026-57516 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (65th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-57516?
CVE-2026-57516 has a CVSS base score of 8.8 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-57516?
A fix for CVE-2026-57516 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-57516 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-57516

Explore →

Is Your Infrastructure Affected by CVE-2026-57516?

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