CVE-2025-62593

CRITICALNVD 8.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2026-08-17), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, nvd
Trending — 4 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 17%CVSS: 8.8Exploit: cisa kev · ssvc active · epss top5pct · public exploitExposed: 0

A fix is available — apply it.

Ray is an AI compute engine. Prior to version 2.52.0, developers working with Ray as a development tool can be exploited via a critical RCE vulnerability exploitable via Firefox and Safari. This vulnerability is due to an insufficient guard against browser-based attacks, as the current defense uses the User-Agent header starting with the string "Mozilla" as a defense mechanism. This defense is insufficient as the fetch specification allows the User-Agent header to be modified. Combined with a DNS rebinding attack against the browser, and this vulnerability is exploitable against a developer running Ray who inadvertently visits a malicious website, or is served a malicious advertisement (malvertising). This issue has been patched in version 2.52.0.

CVSS v3
8.8
EG Score
9.0(high)
EG Risk
96(Act)
EG Risk 96/100SSVC: Act

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
Severity90% × 45%
Exploitation100% × 40%
Automatability100% × 15%
Action: Fix now — active exploitation, automatable, high impact.
EPSS PROB
17%
EPSS %ILE
97%
KEV
⚠ Exploited

Published

November 26, 2025

Last Modified

August 18, 2026

Advisory Details (2)

Auto-updated Jul 31, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available

Critical RCE Vulnerability against Ray Devs exploitable via Browser (Safari & Firefox) due to DNS Rebinding Attack · Advisory · ray-project/ray · GitHub

https://github.com/ray-project/ray/security/advisories/GHSA-q279-jhrf-cc6v
github_commit

commit 70e7c72780bd (ray-project/ray)

Fix landed in ray-project/ray commit 70e7c72780bd — awaiting tagged release

https://github.com/ray-project/ray/commit/70e7c72780bdec075dba6cad1afe0832772bfe09

Vendor Advisories for CVE-2025-62593(10)

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

Patch Availability(10)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhaiis/vllm-cuda-rhel9:17878605802026-08-31redhat
redhatrhoai/odh-vllm-gaudi-rhel9:17709560342026-03-04redhat
redhatrhaiis/vllm-cuda-rhel9:17721605932026-02-27redhat
redhatrhaiis/vllm-rocm-rhel9:17721606252026-02-27redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17682536282026-01-22redhat
redhatrhoai/odh-kserve-storage-initializer-rhel9:v2.25.1-17653265132025-12-17redhat
redhatrhaiis/vllm-cuda-rhel9:3.2.5-17655525802025-12-15redhat
redhatrhaiis/vllm-rocm-rhel9:3.2.2-17653790492025-12-10redhat
redhatrhaiis/model-opt-cuda-rhel9:3.2.2-17648717962025-12-10redhat
redhatrhaiis/vllm-cuda-rhel9:3.2.2-17653790882025-12-10redhat

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
ray0.1.1 ... 2.9.3 (121 versions)2.52.0—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 51× in last 7d / 200× 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 342 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCBoreas37/CVE-2025-62593-PoC
    First seen Aug 18, 2026

    PoC for CVE-2025-62593: unauthenticated RCE in Ray (CISA KEV). Stdlib-only Python.

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(6)

What is CVE-2025-62593?
CVE-2025-62593 is a critical vulnerability published on November 26, 2025. Ray is an AI compute engine. Prior to version 2.52.0, developers working with Ray as a development tool can be exploited via a critical RCE vulnerability exploitable via Firefox and Safari. This vulnerability is due to an insufficient guard against browser-based attacks, as the current defense uses…
When was CVE-2025-62593 disclosed?
CVE-2025-62593 was first published in the National Vulnerability Database on November 26, 2025, with the most recent update on August 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-62593 actively exploited?
Yes. CISA added CVE-2025-62593 to the Known Exploited Vulnerabilities catalog on August 17, 2026, affecting Ray-Project Ray. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2025-62593?
CVE-2025-62593 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
Which products are affected by CVE-2025-62593?
CVE-2025-62593 affects Ray-Project Ray. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2025-62593?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-62593, 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-2025-62593

Explore →

Is Your Infrastructure Affected by CVE-2025-62593?

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

Start Free Scan →Browse All CVEs