Ray is vulnerable to Critical RCE via Safari & Firefox Browsers through DNS Rebinding Attack
CVE-2025-62593 · GHSA-q279-jhrf-cc6v · published 2025-11-26 · updated 2025-12-01
- Severity
- Critical
- CVSS score
- 9.4
- Chance of exploitation (EPSS)
- 60.2%
- Fixed in
- 2.52.0
Known exploited
CISA added this to its Known Exploited Vulnerabilities catalog on 2026-08-17; US federal agencies had until 2026-08-20 to act. CISA's required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk. CISA also asks for forensic triage: look for signs of compromise, not only for the patch.
- Exploitation Exploited in the wild
- Automatable Yes
- Technical impact Total
- CISA SSVC
This vulnerability impacts developers running development/testing environments with Ray. If they fall victim to a phishing attack, or are served a malicious ad, they can be exploited and arbitrary shell code can be executed on their developer machine. This attack can also be leveraged to attack network-adjacent instance of ray by leveraging the browser as a confused deputy intermediary to attack ray instances running inside a private corporate network.
Upgrade ray to 2.52.0 or later.
The fix for this vulnerability is to update to Ray 2.52.0 or higher. This version also, finally, adds a disabled-by-default authentication feature that can further harden against this vulnerability: https://docs.ray.io/en/latest/ray-security/token-auth.html Fix commit: https://github.com/ray-project/ray/commit/70e7c72780bdec075dba6cad1afe0832772bfe09 Several browsers have, after knowing about the attack for 19 years, recently begun hardening against DNS rebinding. (Chrome Local Network Access). These changes may protect you, but a previous initiative, "private network access" was rolled back. So updating is highly recommended as a defense-in-depth strategy.
https://github.com/ray-project/ray/blob/f39a860436dca3ed5b9dfae84bd867ac10c84dc6/python/ray/dashboard/optionalutils.py#L129-L155 https://github.com/ray-project/ray/blob/e7889ae542bf0188610bc8b06d274cbf53790cbd/python/ray/dashboard/httpserver_head.py#L184-L196 This is because the fundamental assumption that the User-Agent header can't be manipulated is incorrect. In Firefox and in Safari, the fetch API allows the User-Agent header to be set to a different value. Chrome is not vulnerable, ironically, because of a bug, bringing it out of spec with the fetch specification. Exploiting this vulnerability requires a DNS rebinding attack against the browser.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| ray | PyPI | < 2.52.0 | 2.52.0 |
- CriticalUnauthenticated Remote Code Execution in Langflow via Public Flow Build EndpointlangflowExploited
- CriticalLangflow Unauth RCElangflow, langflow-baseExploited
- HighLiteLLM: Authenticated command execution via MCP stdio test endpointslitellmExploited
- CriticalMLflow vulnerable to remote code execution on unauthenticated servers via third-party scorer deserialization importing caller-placed artifacmlflow
- CriticalAgno: Arbitrary code execution via `eval()` on `field_type` in `FunctionCall`agno
- CriticalStorybook: Missing origin validation in Storybook preview allows code injection from malicious websites@storybook/addon-mcp, @storybook/addon-mcp
- CriticalRay's New Token Authentication is Disabled By Defaultray
- CriticalRay has arbitrary code execution via jobs submission APIray
- CriticalRay Path Traversal vulnerabilityray
- CriticalRay Missing Authorization vulnerabilityray
- CriticalRay OS Command Injection vulnerabilityray
- HighRay: Arbitrary code execution via ray.data.read_webdataset default decoder: pickle.loads(value) and torch.load(weights_only=False)ray
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.