The Cybersecurity and Infrastructure Security Agency added CVE-2025-62593, a vulnerability in the Ray distributed computing framework, to its Known Exploited Vulnerabilities (KEV) catalog on August 17, 2026, setting an August 20 remediation deadline for federal civilian agencies1.
The compressed three-day window was issued under Binding Operational Directive 26-04, which the agency reserves for vulnerabilities it considers especially risky. The KEV listing signals that the agency has observed active exploitation against unpatched Ray deployments.
CVE-2025-62593 affects Ray versions before 2.52.0. The fix shipped in Ray 2.52.0, released November 26, 2025, and was published in GHSA-q279-jhrf-cc6v on the same date. Anyscale, the company behind Ray, confirmed that every Ray release since 2.52.0 contains the patch.
In a blog post dated August 19, 2026, Anyscale engineer Emre Saglam wrote that the vulnerability was reported through coordinated disclosure and that "what changed this week is CISA's assessment of exploitation activity, rather than the vulnerability itself or the exposure of anyone already on a current release". Saglam noted that a KEV listing "speaks to attacker behavior against unpatched systems" and called it "an important signal for teams that have not upgraded yet".
Anyscale recommends that affected users upgrade to Ray 2.52.0 or later and enable token authentication. Ray 2.52.0 introduced token-based authentication for the dashboard, job submission, and Ray Client. Users can check their installed version by running `ray --version` or `pip show ray`.
ANALYSIS Ray is widely used as infrastructure for distributed AI training and serving workloads, making the KEV listing directly relevant to AI teams running self-managed Ray clusters. The nine-month gap between the patch release in November 2025 and the KEV listing in August 2026 indicates that a meaningful population of Ray deployments remained unpatched long enough to attract active exploitation. The three-day remediation window under Binding Operational Directive 26-04 compresses the typical federal patching timeline and underscores the urgency the agency assigns to this particular vulnerability.