Security Digest · Vulnerability record

CVE-2025-34351: Ray's New Token Authentication is Disabled By Default

Ray's New Token Authentication is Disabled By Default

CVSS 9.3 Critical

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • No confirmed exploitation. It is not in CISA’s KEV catalog. That can change quickly after a public write-up; re-check if you are affected.
  • Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
  • Only applies if your dependency tree includes ray (PyPI) <= 2.52.0, no fixed version listed. Check your lockfile, including transitive dependencies.

What it is

From the GitHub advisory

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.

Weakness type: CWE-304, CWE-1188.

Product: ray (PyPI) · Assigned by: VulnCheck · Published: 2025-11-27

Affected and fixed versions

EcosystemPackageVulnerableFirst fixed
PyPIray<= 2.52.0none listed

Severity scores

Scored byCVSSScoreVector
GitHub4.09.3 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
  • Attack vector: network (remotely reachable)
  • Attack complexity: low
  • Attack requirements: none
  • Privileges required: none (no login)
  • User interaction: none

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).

Timeline

  • — CVE record published by VulnCheck
  • — GitHub-reviewed advisory GHSA-gx77-xgc2-4888 published (critical)
  • — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

  1. GitHub Advisory GHSA-gx77-xgc2-4888 github.com
  2. CVE.org record CVE-2025-34351 cve.org
  3. NVD entry CVE-2025-34351 nvd.nist.gov

Other references from the CVE record and advisory

  1. github.com github.com
  2. docs.ray.io docs.ray.io
  3. vulncheck.com vulncheck.com
  4. github.com github.com
  5. cve.org cve.org
  6. linkedin.com linkedin.com
  7. oligo.security oligo.security
  8. oligo.security oligo.security

Critical PyPI advisories · Today’s Security Digest