CISA orders US federal agencies to patch actively exploited Ray RCE bug within three days

CISA’s three-day remediation window for CVE-2025-62593 reflects the urgency of addressing this actively exploited vulnerability. The bug, rated 9.4 under CVSS v4, enables remote code execution through browser-based attacks, specifically targeting developers running Ray in local or testing environments. The exploit leverages Firefox or Safari’s ability to modify the User-Agent header, bypassing Ray’s rudimentary request filtering. This attack vector is particularly concerning because it requires minimal user interaction, visiting a malicious website or ad is sufficient to trigger the exploit.

The vulnerability stems from Ray’s historical security model, which assumes clusters operate within a trusted, isolated network. This design choice left critical endpoints without built-in authentication, relying instead on external infrastructure for access control. While Ray 2.52.0 introduced optional token-based authentication, it remains disabled by default, and the project continues to recommend network isolation as the primary defense. The lack of default protections increases the risk for organizations that may not implement additional security measures, especially in development environments where isolation is often less stringent.

The impact of this vulnerability extends beyond federal agencies, given Ray’s widespread adoption. With over 237 million downloads and usage by 60% of Fortune 500 companies, the potential attack surface is significant. The exploit can also propagate within private corporate networks, using a compromised developer machine as a pivot point to target adjacent Ray instances. This lateral movement capability amplifies the risk, particularly in environments where Ray clusters are deployed without strict network segmentation or authentication controls.

CISA’s directive highlights the need for rapid patching, but the underlying issue underscores broader challenges in securing open-source frameworks. Ray’s growth, driven by its ease of use for scaling Python and machine-learning workloads, has outpaced its security hardening. The project’s reliance on network isolation as a primary defense is increasingly insufficient in modern, distributed environments. Organizations using Ray must prioritize patching to version 2.52.0 or later, enable optional authentication, and reassess their network security assumptions to mitigate similar risks in the future.