CVE-2025-34351: Ray Package Token Authentication Disabled by Default
Summary
CVE-2025-34351: Ray's New Token Authentication is Disabled By Default. Affects ray versions < 2.52.0. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Anyscale Ray is an open-source framework designed for building and running distributed applications. It provides a simple interface for parallel and distributed computing, enabling users to scale their Python applications effortlessly. However, in version 2.52.0, Ray has an insecure default configuration where token-based authentication for its management interfaces, including the dashboard and Jobs API, is disabled unless explicitly enabled. This poses a significant security risk.
Vulnerability Detail
The vulnerability arises from the default configuration of Anyscale Ray 2.52.0, where token-based authentication is turned off. This means that if the user does not enable authentication, a remote attacker with network access can exploit this weakness to submit jobs and execute arbitrary code on the Ray cluster. The lack of authentication can lead to unauthorized access and control over the cluster, potentially resulting in data breaches or service disruptions.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a temporary workaround, you can manually enable token authentication by setting the environment variable as follows: export RAY_AUTH_MODE=token. This will help secure your Ray management interfaces until a patched version is available.
Conclusion
In summary, the vulnerability in Anyscale Ray 2.52.0 stems from the default disabled state of token-based authentication, which can lead to unauthorized access and control over the cluster. Users are advised to enable authentication and monitor for updates from the vendor to mitigate this risk.
See every vulnerability recorded for ray →
FAQ
The impact includes unauthorized access to the Ray cluster, allowing attackers to submit jobs and execute arbitrary code.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
Currently, there is no patch available, but the vendor plans to enable token authentication by default in a future release.
If you cannot update immediately, ensure to enable token authentication by setting RAY_AUTH_MODE=token as a temporary measure.
Best practices include enabling token authentication, regularly updating to the latest version, and restricting network access to the management interfaces.
Related vulnerabilities
Recent vulnerabilities recorded for ray.
