Ray's New Token Authentication is Disabled By Default
CVE-2025-34351 · GHSA-gx77-xgc2-4888 · published 2025-11-27 · updated 2025-12-01
- Severity
- Critical
- CVSS score
- 9.3
- Chance of exploitation (EPSS)
- 0.47%
- Fixed in
- No fix yet
Anyscale Ray 2.52.0 contains an insecure default configuration in which token-based authentication for Ray management interfaces (including the dashboard and Jobs API) is disabled unless explicitly enabled by setting RAY_AUTH_MODE=token. In the default unauthenticated state, a remote attacker with network access to these interfaces can submit jobs and execute arbitrary code on the Ray cluster. NOTE: The vendor plans to enable token authentication by default in a future release. They recommend enabling token authentication to protect your cluster from unauthorized access.
No fixed release is listed yet for ray. Follow the source advisory for updates, and until one ships:
General guidance from ShieldPi, not a vendor fix
- Missing or bypassable authentication. Do not expose it on a network others can reach, and put authentication you control in front of it, such as an authenticating proxy or a VPN. Binding it to localhost is not enough on its own: a web page open in your browser can still reach it, so require a token as well.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| ray | PyPI | <= 2.52.0 | No fix yet |
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- CriticalRay is vulnerable to Critical RCE via Safari & Firefox Browsers through DNS Rebinding AttackrayExploited
- 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.