Ray users should update to 2.52.0 or later now. CISA added CVE-2025-62593 to its Known Exploited Vulnerabilities catalog on August 17, 2026. The upstream Ray security advisory rates the issue critical and identifies Ray releases before 2.52.0 as affected.
Ray is commonly used for distributed Python workloads, machine-learning platforms, internal compute clusters, and development environments. Treat this as a priority maintenance item wherever Ray is installed or bundled into a managed platform.
What Administrators Need To Know
- CISA lists CVE-2025-62593 in its Known Exploited Vulnerabilities catalog.
- The official Ray advisory identifies 2.52.0 as the first patched release.
- Risk is greatest when workload, developer, or management services are reachable from less-trusted networks.
Update Plan
- Inventory systems, containers, CI jobs, and managed services that include Ray.
- Schedule a small maintenance window that matches the workload’s normal release process.
- Update Ray to 2.52.0 or later through the supported package, image, or platform workflow.
- Restart or roll workloads only inside the approved change window.
- Confirm the running version, worker health, job completion, and expected access controls after the change.
Reduce Exposure Until The Update Is Complete
- Keep Ray workload and management services on private or administrator-only networks.
- Remove temporary public exposure and stale development access.
- Review firewall, identity, and proxy rules around the affected environment.
- Monitor normal security and platform telemetry for unusual access, then follow your incident process if needed.
Hosting And Platform Team Notes
Check machine-learning, CI, orchestration, and customer-managed environments separately. A Ray dependency may live inside an image or application platform even when the host package inventory does not show a direct installation. Communicate the maintenance window, the affected service owner, and the verification step before rolling customer-facing workloads.
Related FixItPhill Guidance
Use the WordPress support hub for site-owner maintenance guidance, review the Docker Desktop Model Runner patch guide for another platform-update example, and keep a Linux hosting maintenance checklist handy when planning service work.