CVE-2025-34351: PYSEC-2026-518 - Ray's New Token Authentication is Disabled By Default
CVE-2025-34351 · Severity: medium · CVSS 4 · Published 2025-11-27
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).
No. Junglewise Threat Intelligence has no report of CVE-2025-34351 being exploited in the wild.
How severe is CVE-2025-34351?
Medium severity, with a CVSS score of 4, published 27 November 2025.
Which products and versions are affected?
ray (PyPI) ECOSYSTEM:introduced=0,last_affected=2.52.0.
Is there a fix for CVE-2025-34351?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2025-34351?
Check whether you run ray (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Affected products
ray (PyPI) ECOSYSTEM:introduced=0,last_affected=2.52.0