Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-gx77-xgc2-4888 | Ray's New Token Authentication is Disabled By Default |
No reference.
Tue, 09 Dec 2025 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | 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). |
Tue, 02 Dec 2025 22:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-1188 | |
| References |
|
|
| Metrics |
cvssV4_0
|
Tue, 02 Dec 2025 22:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | 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. |
| Title | Anyscale Ray v2.52.0 Token Authentication Disabled by Default Insecure Configuration | |
| CPEs | ||
| Metrics |
cvssV4_0
|
cvssV4_0
|
Fri, 28 Nov 2025 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:anyscale:ray:2.52.0:*:*:*:*:*:*:* |
Thu, 27 Nov 2025 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Anyscale
Anyscale ray |
|
| Vendors & Products |
Anyscale
Anyscale ray |
Thu, 27 Nov 2025 03:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Anyscale Ray v2.52.0 Token Authentication Disabled by Default Insecure Configuration | |
| Weaknesses | CWE-1188 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: REJECTED
Assigner: VulnCheck
Published:
Updated: 2025-12-09T19:11:41.458Z
Reserved: 2025-04-15T19:15:22.589Z
Link: CVE-2025-34351
No data.
Status : Rejected
Published: 2025-11-27T03:15:58.790
Modified: 2025-12-09T20:15:53.973
Link: CVE-2025-34351
No data.
OpenCVE Enrichment
Updated: 2025-11-27T16:26:37Z
No weakness.
Github GHSA