critical9.3
CVE-2025-34351
Ray's New Token Authentication is Disabled By Default
Impact
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.
Affected packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| pip | ray | <= 2.52.0 | none recorded |
Weakness classification
References
- NVD record
- CVE.org record
- GitHub advisory
- https://github.com/advisories/GHSA-gx77-xgc2-4888
- https://github.com/JLLeitschuh/security-research/security/advisories/GHSA-w8vc-465m-jjw6
- https://nvd.nist.gov/vuln/detail/CVE-2025-34351
- https://docs.ray.io/en/latest/ray-security/token-auth.html
- https://www.vulncheck.com/advisories/anyscale-ray-token-authentication-disabled-by-default-insecure-configuration
- https://github.com/ray-project/ray/releases/tag/ray-2.52.0
- https://www.cve.org/resourcessupport/allresources/cnarules#section_4-1_Vulnerability_Determination
- https://www.linkedin.com/posts/jonathan-leitschuh_the-latest-piece-of-mind-bending-research-activity-7396976425997606912-qizE
- https://www.oligo.security/blog/shadowray-2-0-attackers-turn-ai-against-itself-in-global-campaign-that-hijacks-ai-into-self-propagating-botnet
- https://www.oligo.security/blog/shadowray-attack-ai-workloads-actively-exploited-in-the-wild