← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

Is CVE-2025-62593 exploited? Yes: in CISA KEV since 17 Aug 2026

Gociux · Ray-Project Ray · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2025-62593, Ray-Project Ray Code Injection Vulnerability, is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 17 Aug 2026, 264 days after it was published. It affects Ray-Project Ray. If you run it, CISA's required action is: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

exploitedYesCISA KEV · 17 Aug 2026
ransomwareNot knownno confirmed use
EPSStop 1%among the most likely CVEs to be exploited
severity9.4CVSS 4.0 · critical
US federal due20 Aug 2026BOD 22-01 deadline

What it is

Ray-Project Ray contains a code injection vulnerability that could allow remote code execution. Developers using Ray as a development tool may be exposed to this vulnerability exploitable through Firefox and Safari.

VendorRay-Project (1 exploited CVE in KEV)
ProductRay
VulnerabilityRay-Project Ray Code Injection Vulnerability
WeaknessCWE-94, CWE-352
Published26 Nov 2025
Added to KEV17 Aug 2026
Reported by (CNA)GitHub_M

What to do

  1. Check whether you run it. Look for Ray in your asset inventory, including appliances and cloud images. Stack check lists every exploited Ray-Project CVE at once.
  2. Apply the fix. Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
  3. If you can't patch today, take the affected service off the internet or restrict who can reach it, and check its logs for signs of compromise since 26 Nov 2025.
  4. Get told next time. Email alerts when CISA adds a CVE for Ray-Project.

References

Questions

Is CVE-2025-62593 being exploited?

Yes. CISA added CVE-2025-62593 to the Known Exploited Vulnerabilities catalog on 17 Aug 2026, which means there is reliable evidence of exploitation in the wild.

Is CVE-2025-62593 used in ransomware attacks?

CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.

How do I fix CVE-2025-62593?

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. Check Ray-Project's advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected Ray and watch it for signs of compromise.

Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in August 2026 · act-now radar.

Running Ray-Project in a regulated environment?

We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.

Get in touch →