CVE-2025-34351: Anyscale Ray v2.52.0 Token Authentication Disabled by Default Insecure Configuration
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 RAYAUTHMODE=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.
Other sources
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 has been determined that this assignment did not identify a valid vulnerability based on the vendor's product security model.
— NVD
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-34351?
CVE-2025-34351 is considered a high severity vulnerability due to its potential for unauthorized access.
How do I fix CVE-2025-34351?
To fix CVE-2025-34351, explicitly enable token-based authentication by setting RAY_AUTH_MODE=token in your configuration.
What are the risks associated with CVE-2025-34351?
The risks associated with CVE-2025-34351 include exposure of sensitive data and unauthorized operations on the Ray management interfaces.
Which versions of Anyscale Ray are affected by CVE-2025-34351?
CVE-2025-34351 affects Anyscale Ray version 2.52.0.
Is CVE-2025-34351 a configuration issue?
Yes, CVE-2025-34351 is a configuration issue due to the insecure default setting that disables authentication.