<?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, 02 Oct 2026 13:39:35 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-225499</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-225499</link>
      <description>EUVD-2026-225499</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-225499</guid>
    </item>
    <item>
      <title>fkie_cve-2023-0591</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-0591</link>
      <description>&lt;p&gt;ubireader_extract_files is vulnerable to path traversal when run against specifically crafted UBIFS files, allowing the attacker to overwrite files outside of the extraction directory (provided the process has write access to that file or directory).&lt;/p&gt;
&lt;p&gt;This is due to the fact that a node name (dent_node.name) is considered trusted and joined to the extraction directory path during processing, then the node content is written to that joined path. By crafting a malicious UBIFS file with node names holding path traversal payloads (e.g. ../../tmp/outside.txt), it&amp;#39;s possible to force ubi_reader to write outside of the extraction directory.&lt;/p&gt;
&lt;p&gt;This issue affects ubi-reader before 0.8.5.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;ubireader_extract_files is vulnerable to path traversal when run against specifically crafted UBIFS files, allowing the attacker to overwrite files outside of the extraction directory (provided the process has write access to that file or directory).&lt;/p&gt;
&lt;p&gt;This is due to the fact that a node name (dent_node.name) is considered trusted and joined to the extraction directory path during processing, then the node content is written to that joined path. By crafting a malicious UBIFS file with node names holding path traversal payloads (e.g. ../../tmp/outside.txt), it&amp;#39;s possible to force ubi_reader to write outside of the extraction directory.&lt;/p&gt;
&lt;p&gt;This issue affects ubi-reader before 0.8.5.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-0591</guid>
    </item>
    <item>
      <title>GHSA-vp2x-3mc3-3cj4 — Path traversal in ubi-reader</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vp2x-3mc3-3cj4</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: ubi-reader&lt;/p&gt;
&lt;p&gt;ubireader_extract_files is vulnerable to path traversal when run against specifically crafted UBIFS files, allowing the attacker to overwrite files outside of the extraction directory (provided the process has write access to that file or directory). This is due to the fact that a node name (dent_node.name) is considered trusted and joined to the extraction directory path during processing, then the node content is written to that joined path. By crafting a malicious UBIFS file with node names holding path traversal payloads (e.g. ../../tmp/outside.txt), it&amp;#39;s possible to force ubi_reader to write outside of the extraction directory. This issue affects ubi-reader before 0.8.5.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: ubi-reader&lt;/p&gt;
&lt;p&gt;ubireader_extract_files is vulnerable to path traversal when run against specifically crafted UBIFS files, allowing the attacker to overwrite files outside of the extraction directory (provided the process has write access to that file or directory). This is due to the fact that a node name (dent_node.name) is considered trusted and joined to the extraction directory path during processing, then the node content is written to that joined path. By crafting a malicious UBIFS file with node names holding path traversal payloads (e.g. ../../tmp/outside.txt), it&amp;#39;s possible to force ubi_reader to write outside of the extraction directory. This issue affects ubi-reader before 0.8.5.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vp2x-3mc3-3cj4</guid>
    </item>
    <item>
      <title>gsd-2023-0591</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-0591</link>
      <description>gsd-2023-0591</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-0591</guid>
    </item>
    <item>
      <title>PYSEC-2023-51</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2023-51</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: ubi-reader&lt;/p&gt;
&lt;p&gt;ubireader_extract_files is vulnerable to path traversal when run against specifically crafted UBIFS files, allowing the attacker to overwrite files outside of the extraction directory (provided the process has write access to that file or directory). This is due to the fact that a node name (dent_node.name) is considered trusted and joined to the extraction directory path during processing, then the node content is written to that joined path. By crafting a malicious UBIFS file with node names holding path traversal payloads (e.g. ../../tmp/outside.txt), it&amp;#39;s possible to force ubi_reader to write outside of the extraction directory. This issue affects ubi-reader before 0.8.5.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: ubi-reader&lt;/p&gt;
&lt;p&gt;ubireader_extract_files is vulnerable to path traversal when run against specifically crafted UBIFS files, allowing the attacker to overwrite files outside of the extraction directory (provided the process has write access to that file or directory). This is due to the fact that a node name (dent_node.name) is considered trusted and joined to the extraction directory path during processing, then the node content is written to that joined path. By crafting a malicious UBIFS file with node names holding path traversal payloads (e.g. ../../tmp/outside.txt), it&amp;#39;s possible to force ubi_reader to write outside of the extraction directory. This issue affects ubi-reader before 0.8.5.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2023-51</guid>
    </item>
  </channel>
</rss>
