CVE-2026-57516

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.9%, top 44% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: Elevated riskExposed: 0

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

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.8(medium)
EG Risk
56(Track*)
EG Risk 56/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
Severity88% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
56%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 14, 2026

Advisory Details (5)

Auto-updated Jul 1, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github, github_pr.
github Patch Available🟡 PoC Available

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
generic

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_pr

[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_pr

[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

Vendor Advisories for CVE-2026-57516(2)

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

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
ray0.1.1 ... 2.9.3 (128 versions)2.56.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 48× 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 112 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-57516?
CVE-2026-57516 is a high vulnerability 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 readwebdataset() function. The defaultdecoder() function in webdatasetdatasource.py unconditionally calls…
When was CVE-2026-57516 disclosed?
CVE-2026-57516 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57516 actively exploited?
CVE-2026-57516 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 44.0% of all scored CVEs.
What is the CVSS score of CVE-2026-57516?
CVE-2026-57516 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-57516?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57516, 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-57516

Explore →

Is Your Infrastructure Affected by CVE-2026-57516?

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

Start Free Scan →Browse All CVEs