<?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>Thu, 15 Oct 2026 23:40:12 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-47084 — CORS origin validation is not performed when the request has a cookie in Gradio</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-47084</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; gradio-app gradio, gradio_project gradio&lt;/p&gt;
&lt;p&gt;Gradio is an open-source Python package designed for quick prototyping. This vulnerability is related to **CORS origin validation**, where the Gradio server fails to validate the request origin when a cookie is present. This allows an attacker’s website to make unauthorized requests to a local Gradio server. Potentially, attackers can upload files, steal authentication tokens, and access user data if the victim visits a malicious website while logged into Gradio. This impacts users who have deployed Gradio locally and use basic authentication. Users are advised to upgrade to `gradio&amp;gt;4.44` to address this issue. As a workaround, users can manually enforce stricter CORS origin validation by modifying the `CustomCORSMiddleware` class in their local Gradio server code. Specifically, they can bypass the condition that skips CORS validation for requests containing cookies to prevent potential exploitation.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; gradio-app gradio, gradio_project gradio&lt;/p&gt;
&lt;p&gt;Gradio is an open-source Python package designed for quick prototyping. This vulnerability is related to **CORS origin validation**, where the Gradio server fails to validate the request origin when a cookie is present. This allows an attacker’s website to make unauthorized requests to a local Gradio server. Potentially, attackers can upload files, steal authentication tokens, and access user data if the victim visits a malicious website while logged into Gradio. This impacts users who have deployed Gradio locally and use basic authentication. Users are advised to upgrade to `gradio&amp;gt;4.44` to address this issue. As a workaround, users can manually enforce stricter CORS origin validation by modifying the `CustomCORSMiddleware` class in their local Gradio server code. Specifically, they can bypass the condition that skips CORS validation for requests containing cookies to prevent potential exploitation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-47084</guid>
    </item>
    <item>
      <title>GHSA-3c67-5hwx-f6wx — Gradios's CORS origin validation is not performed when the request has a cookie</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3c67-5hwx-f6wx</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: gradio&lt;/p&gt;
&lt;p&gt;### Impact
**What kind of vulnerability is it? Who is impacted?**&lt;/p&gt;
&lt;p&gt;This vulnerability is related to **CORS origin validation**, where the Gradio server fails to validate the request origin when a cookie is present. This allows an attacker’s website to make unauthorized requests to a local Gradio server. Potentially, attackers can upload files, steal authentication tokens, and access user data if the victim visits a malicious website while logged into Gradio. This impacts users who have deployed Gradio locally and use basic authentication.&lt;/p&gt;
&lt;p&gt;### Patches
Yes, please upgrade to `gradio&amp;gt;=4.44` to address this issue.&lt;/p&gt;
&lt;p&gt;### Workarounds
**Is there a way for users to fix or remediate the vulnerability without upgrading?**&lt;/p&gt;
&lt;p&gt;As a workaround, users can manually enforce stricter CORS origin validation by modifying the `CustomCORSMiddleware` class in their local Gradio server code. Specifically, they can bypass the condition that skips CORS validation for requests containing cookies to prevent potential exploitation.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: gradio&lt;/p&gt;
&lt;p&gt;### Impact
**What kind of vulnerability is it? Who is impacted?**&lt;/p&gt;
&lt;p&gt;This vulnerability is related to **CORS origin validation**, where the Gradio server fails to validate the request origin when a cookie is present. This allows an attacker’s website to make unauthorized requests to a local Gradio server. Potentially, attackers can upload files, steal authentication tokens, and access user data if the victim visits a malicious website while logged into Gradio. This impacts users who have deployed Gradio locally and use basic authentication.&lt;/p&gt;
&lt;p&gt;### Patches
Yes, please upgrade to `gradio&amp;gt;=4.44` to address this issue.&lt;/p&gt;
&lt;p&gt;### Workarounds
**Is there a way for users to fix or remediate the vulnerability without upgrading?**&lt;/p&gt;
&lt;p&gt;As a workaround, users can manually enforce stricter CORS origin validation by modifying the `CustomCORSMiddleware` class in their local Gradio server code. Specifically, they can bypass the condition that skips CORS validation for requests containing cookies to prevent potential exploitation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3c67-5hwx-f6wx</guid>
    </item>
  </channel>
</rss>
