Ray's New Token Authentication is Disabled By Default
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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2025-34351US | —OT elevated | — | ||
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. At the request of the MITRE TL-Root and following the CVE Program’s Dispute Policy, it h… | ||||
references
External citations — patches, advisories, analysis.
- https://docs.ray.io/en/latest/ray-security/token-auth.htmlWEB
- https://github.com/JLLeitschuh/security-research/security/advisories/GHSA-w8vc-465m-jjw6WEB
- https://github.com/advisories/GHSA-gx77-xgc2-4888ADVISORY
- https://github.com/ray-project/rayPACKAGE
- https://github.com/ray-project/ray/releases/tag/ray-2.52.0WEB
- https://nvd.nist.gov/vuln/detail/CVE-2025-34351ADVISORY
- https://pypi.org/project/rayPACKAGE
- https://www.cve.org/resourcessupport/allresources/cnarules#section_4-1_Vulnerability_DeterminationWEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan