<?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>Fri, 23 Oct 2026 10:26:21 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-195112</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-195112</link>
      <description>EUVD-2026-195112</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-195112</guid>
    </item>
    <item>
      <title>fkie_cve-2024-47166</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-47166</link>
      <description>&lt;p&gt;Gradio is an open-source Python package designed for quick prototyping. This vulnerability involves a **one-level read path traversal** in the `/custom_component` endpoint. Attackers can exploit this flaw to access and leak source code from custom Gradio components by manipulating the file path in the request. Although the traversal is limited to a single directory level, it could expose proprietary or sensitive code that developers intended to keep private. This impacts users who have developed custom Gradio components and are hosting them on publicly accessible servers. Users are advised to upgrade to `gradio&amp;gt;=4.44` to address this issue. As a workaround, developers can sanitize the file paths and ensure that components are not stored in publicly accessible directories.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Gradio is an open-source Python package designed for quick prototyping. This vulnerability involves a **one-level read path traversal** in the `/custom_component` endpoint. Attackers can exploit this flaw to access and leak source code from custom Gradio components by manipulating the file path in the request. Although the traversal is limited to a single directory level, it could expose proprietary or sensitive code that developers intended to keep private. This impacts users who have developed custom Gradio components and are hosting them on publicly accessible servers. Users are advised to upgrade to `gradio&amp;gt;=4.44` to address this issue. As a workaround, developers can sanitize the file paths and ensure that components are not stored in publicly accessible directories.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-47166</guid>
    </item>
    <item>
      <title>GHSA-37qc-qgx6-9xjv — Gradio has a one-level read path traversal in `/custom_component`</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-37qc-qgx6-9xjv</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 involves a **one-level read path traversal** in the `/custom_component` endpoint. Attackers can exploit this flaw to access and leak source code from custom Gradio components by manipulating the file path in the request. Although the traversal is limited to a single directory level, it could expose proprietary or sensitive code that developers intended to keep private. This impacts users who have developed custom Gradio components and are hosting them on publicly accessible servers.&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, developers can sanitize the file paths and ensure that components are not stored in publicly accessible directories.&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 involves a **one-level read path traversal** in the `/custom_component` endpoint. Attackers can exploit this flaw to access and leak source code from custom Gradio components by manipulating the file path in the request. Although the traversal is limited to a single directory level, it could expose proprietary or sensitive code that developers intended to keep private. This impacts users who have developed custom Gradio components and are hosting them on publicly accessible servers.&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, developers can sanitize the file paths and ensure that components are not stored in publicly accessible directories.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-37qc-qgx6-9xjv</guid>
    </item>
    <item>
      <title>PYSEC-2024-197</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2024-197</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: gradio&lt;/p&gt;
&lt;p&gt;Gradio is an open-source Python package designed for quick prototyping. This vulnerability involves a **one-level read path traversal** in the `/custom_component` endpoint. Attackers can exploit this flaw to access and leak source code from custom Gradio components by manipulating the file path in the request. Although the traversal is limited to a single directory level, it could expose proprietary or sensitive code that developers intended to keep private. This impacts users who have developed custom Gradio components and are hosting them on publicly accessible servers. Users are advised to upgrade to `gradio&amp;gt;=4.44` to address this issue. As a workaround, developers can sanitize the file paths and ensure that components are not stored in publicly accessible directories.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: gradio&lt;/p&gt;
&lt;p&gt;Gradio is an open-source Python package designed for quick prototyping. This vulnerability involves a **one-level read path traversal** in the `/custom_component` endpoint. Attackers can exploit this flaw to access and leak source code from custom Gradio components by manipulating the file path in the request. Although the traversal is limited to a single directory level, it could expose proprietary or sensitive code that developers intended to keep private. This impacts users who have developed custom Gradio components and are hosting them on publicly accessible servers. Users are advised to upgrade to `gradio&amp;gt;=4.44` to address this issue. As a workaround, developers can sanitize the file paths and ensure that components are not stored in publicly accessible directories.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2024-197</guid>
    </item>
  </channel>
</rss>
