CVE-2025-34351
Ray's New Token Authentication is Disabled By Default
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. Additionally, this assignment conflicts with an existing CVE (CVE-2023-48022).
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
What each source reports
GitHub Advisories Score usedGHSA-gx77-xgc2-4888
9.3
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.
- Record
GHSA-gx77-xgc2-4888- CVSS 4.0
- 9.3 Critical
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N - Weakness
- CWE-304, CWE-1188
- Updated
- 2026-11-02
CVE List No score
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. Additionally, this assignment conflicts with an existing CVE (CVE-2023-48022).
- Record
CVE-2025-34351- Updated
- 2026-11-02
EUVDEUVD-2025-199783 No score
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. Additionally, this assignment conflicts with an existing CVE (CVE-2023-48022).
- Record
EUVD-2025-199783- Updated
- 2026-11-02
NVD No score
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. Additionally, this assignment conflicts with an existing CVE (CVE-2023-48022).
- Record
CVE-2025-34351- Updated
- 2026-11-02
OSVGHSA-gx77-xgc2-4888
9.3
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.
- Record
GHSA-gx77-xgc2-4888- CVSS 4.0
- 9.3 Critical
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N - Weakness
- CWE-1188, CWE-304
- Updated
- 2026-11-02
OSVPYSEC-2026-518
9.3
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.
- Record
PYSEC-2026-518- CVSS 4.0
- 9.3 Critical
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N - Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
rayPyPI |
through 2.52.0 | None known |
rayPyPI |
through 2.52.0, plus listed versions 0.1.10.1.20.2.00.2.10.2.2 Show 45 moreShow less0.3.00.3.10.4.00.5.00.5.20.5.30.6.00.6.10.6.20.6.30.6.40.6.50.6.60.7.00.7.10.7.20.7.30.7.40.7.50.7.60.7.70.8.00.8.10.8.20.8.30.8.40.8.50.8.60.8.71.0.01.0.11.1.01.10.01.11.01.11.11.12.01.12.11.13.01.2.01.3.01.4.01.4.11.5.01.5.11.5.2 |
None known |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2025-34351 has been rejected by its source and should not be treated as a live vulnerability, published November 27, 2025.
References
github.com/JLLeitschuh/security-research/security/advisories/GHSA-w8vc-465m-jjw6
nvd.nist.gov/vuln/detail/CVE-2025-34351
docs.ray.io/en/latest/ray-security/token-auth.html
vulncheck.com/advisories/anyscale-ray-token-authentication-disabled-by-default-insecure-configuration
github.com/ray-project/ray/releases/tag/ray-2.52.0
cve.org/resourcessupport/allresources/cnarules
Show 6 moreShow less
linkedin.com/posts/jonathan-leitschuh_the-latest-piece-of-mind-bending-research-activity-7396976425997606912-qizE
oligo.security/blog/shadowray-2-0-attackers-turn-ai-against-itself-in-global-campaign-that-hijacks-ai-into-self-propagating-botnet
oligo.security/blog/shadowray-attack-ai-workloads-actively-exploited-in-the-wild
github.com/advisories/GHSA-gx77-xgc2-4888
github.com/ray-project/ray
pypi.org/project/ray
Left out here: 71 versions. The JSON record has them.