CVE-2025-62593: Ray is vulnerable to RCE via Safari & Firefox Browsers through DNS Rebinding Attack
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.
Security readout for executives and security teams
Plain-English summary
Ray versions before 2.52.0 can let a malicious website or advertisement turn a developer’s Safari or Firefox browser into a path for remote code execution. Because successful compromise could affect confidentiality, integrity, and availability, exposed development environments should be treated urgently.
Executive priority
Immediate. Assign ownership, identify vulnerable Ray installations, and upgrade them promptly. KEV inclusion raises this above routine patching because exploitation is documented, while the critical impact includes potential code execution and compromise of development assets.
Technical view
Ray’s browser-attack defense relied on the User-Agent header beginning with “Mozilla.” Because the Fetch specification permits modifying that header, an attacker can combine this weakness with DNS rebinding to reach a developer’s Ray service and achieve remote code execution. Version 2.52.0 patches the issue.
Likely exposure
Development systems running Ray below 2.52.0 are affected. Risk exists when a developer using Firefox or Safari visits malicious content or receives malvertising while Ray is running. The supplied sources do not identify specific configurations, operating systems, or deployment boundaries that eliminate exposure.
Exploitation context
CISA lists CVE-2025-62593 in its Known Exploited Vulnerabilities catalog, supporting active exploitation in the wild. The supplied evidence does not establish exploitation scale, named victims, campaign timing, or whether every vulnerable configuration is practically reachable.
Researcher notes
The advisory maps the issue to CWE-352 and CWE-94 and assigns CVSS 4.0 score 9.4. The browser interaction requirement is reflected as UI:P, but no privileges are required. The supplied material does not provide indicators of compromise or enough evidence to characterize observed exploitation beyond KEV status.
Mitigation direction
Upgrade every affected Ray installation to version 2.52.0 or later.
Prioritize developer workstations and environments where Ray runs during web browsing.
Avoid operating vulnerable Ray instances until they can be upgraded.
Check the Ray advisory for any deployment-specific guidance or later updates.
Validation and detection
Inventory Ray versions across developer workstations, servers, containers, and cluster nodes.
Confirm no installation remains below version 2.52.0.
Verify all cluster components and rebuilt images use the patched release.
Review relevant Ray and network telemetry for unexpected access or execution.
Escalate suspicious findings for incident investigation and evidence preservation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
Exploitation: activeAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-352 · source CWE mapping
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.