Skip to content
Threat Feed
high threat exploited

Active Exploitation of Code Injection Vulnerability in Ray

CISA has added CVE-2025-62593, a code injection vulnerability in the Ray framework, to its Known Exploited Vulnerabilities catalog following reports of active exploitation.

CVE search metadata

CVE search record: CVE-2025-62593. EPSS: 0.37%. KEV: no. Product: Ray. Brief: Active Exploitation of Code Injection Vulnerability in Ray. Brief link: https://feed.craftedsignal.io/briefs/2026-08-cve-2025-62593-ray/

What's new

  • 1. new vendor Aug 17, 18:36 via cisa-kev

CISA has officially added CVE-2025-62593 to its Known Exploited Vulnerabilities (KEV) Catalog, citing clear evidence of active exploitation in the wild. This vulnerability affects the Ray project, an open-source framework widely used for scaling distributed AI and Python applications. The flaw is identified as a code injection vulnerability that allows unauthenticated attackers to execute arbitrary code within the context of a Ray cluster. Given the widespread use of Ray in distributed compute environments, this vulnerability presents a significant risk to organizations managing AI infrastructure. As per CISA’s Binding Operational Directive (BOD) 26-04, federal agencies are required to prioritize the remediation of this vulnerability on all publicly exposed assets to prevent complete system compromise.

Impact

Successful exploitation of CVE-2025-62593 enables malicious actors to achieve remote code execution on the targeted Ray cluster. This compromise can lead to full system takeover, data exfiltration from compute nodes, and the potential for lateral movement within the broader organizational network or cloud environment. The criticality of this vulnerability is elevated by its current exploitation status, making it a high-priority target for threat actors seeking to compromise distributed AI compute resources.

Recommendation

  • Immediately audit all public-facing and internal Ray cluster deployments to determine if they are running vulnerable versions impacted by CVE-2025-62593.
  • Apply vendor-provided security patches to all affected Ray instances as the primary mitigation strategy.
  • Implement network segmentation and restrictive firewall policies to ensure that Ray dashboard and API endpoints are not exposed to the public internet.
  • Conduct a review of system logs for unauthorized command execution or unexpected outbound network connections originating from Ray nodes, as per the guidelines in BOD 26-04.