<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 09:09:45 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-62593 — Ray is vulnerable to RCE via Safari &amp; Firefox Browsers through DNS Rebinding Attack</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-62593</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ray-project ray&lt;/p&gt;
&lt;p&gt;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 &amp;#34;Mozilla&amp;#34; 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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ray-project ray&lt;/p&gt;
&lt;p&gt;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 &amp;#34;Mozilla&amp;#34; 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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-62593</guid>
    </item>
    <item>
      <title>GHSA-q279-jhrf-cc6v — Ray is vulnerable to Critical RCE via Safari &amp; Firefox Browsers through DNS Rebinding Attack</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-q279-jhrf-cc6v</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: ray&lt;/p&gt;
&lt;p&gt;# Summary&lt;/p&gt;
&lt;p&gt;Developers working with Ray as a development tool can be exploited via a critical RCE vulnerability exploitable via Firefox and Safari.&lt;/p&gt;
&lt;p&gt;Due to the longstanding [decision](https://docs.ray.io/en/releases-2.51.1/ray-security/index.html) by the Ray Development team to not implement any sort of authentication on critical endpoints, like the `/api/jobs` &amp;amp; `/api/job_agent/jobs/` has once again led to a severe vulnerability that allows attackers to execute arbitrary code against Ray. This time in a development context via the browsers Firefox and Safari.&lt;/p&gt;
&lt;p&gt;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 &amp;#34;Mozilla&amp;#34; as a defense mechanism. This defense is insufficient as the fetch specification allows the `User-Agent` header to be modified.&lt;/p&gt;
&lt;p&gt;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](https://en.wikipedia.org/wiki/Malvertising)).&lt;/p&gt;
&lt;p&gt;# Details&lt;/p&gt;
&lt;p&gt;The mitigations implemented to protect against browser based attacks against local Ray nodes are insufficient.&lt;/p&gt;
&lt;p&gt;## Current Mitigation Strategies&lt;/p&gt;
&lt;p&gt;```python
def is_browser_request(req: Request) -&amp;gt; bool:
    &amp;#34;&amp;#34;&amp;#34;Checks if a request is made by a browser like user agent.&lt;/p&gt;
&lt;p&gt;This heuristic is very weak, but hard for a browser to bypass- eg,
    fetc…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: ray&lt;/p&gt;
&lt;p&gt;# Summary&lt;/p&gt;
&lt;p&gt;Developers working with Ray as a development tool can be exploited via a critical RCE vulnerability exploitable via Firefox and Safari.&lt;/p&gt;
&lt;p&gt;Due to the longstanding [decision](https://docs.ray.io/en/releases-2.51.1/ray-security/index.html) by the Ray Development team to not implement any sort of authentication on critical endpoints, like the `/api/jobs` &amp;amp; `/api/job_agent/jobs/` has once again led to a severe vulnerability that allows attackers to execute arbitrary code against Ray. This time in a development context via the browsers Firefox and Safari.&lt;/p&gt;
&lt;p&gt;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 &amp;#34;Mozilla&amp;#34; as a defense mechanism. This defense is insufficient as the fetch specification allows the `User-Agent` header to be modified.&lt;/p&gt;
&lt;p&gt;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](https://en.wikipedia.org/wiki/Malvertising)).&lt;/p&gt;
&lt;p&gt;# Details&lt;/p&gt;
&lt;p&gt;The mitigations implemented to protect against browser based attacks against local Ray nodes are insufficient.&lt;/p&gt;
&lt;p&gt;## Current Mitigation Strategies&lt;/p&gt;
&lt;p&gt;```python
def is_browser_request(req: Request) -&amp;gt; bool:
    &amp;#34;&amp;#34;&amp;#34;Checks if a request is made by a browser like user agent.&lt;/p&gt;
&lt;p&gt;This heuristic is very weak, but hard for a browser to bypass- eg,
    fetc…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-q279-jhrf-cc6v</guid>
    </item>
  </channel>
</rss>
