<?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>Tue, 06 Oct 2026 16:16:29 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-349562</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-349562</link>
      <description>EUVD-2026-349562</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-349562</guid>
    </item>
    <item>
      <title>fkie_cve-2026-66485</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-66485</link>
      <description>&lt;p&gt;GNU cpio is vulnerable to an uncontrolled memory allocation in the make_path function at src/makepath.c. The function uses alloca to allocate stack memory based on the length of argpath, which is derived from an archive-controlled pathname during extraction. A malicious cpio archive containing a sufficiently long nested pathname causes an unbounded stack allocation, resulting in a stack overflow and crash of the cpio process. An attacker who can supply a crafted cpio archive to a victim who extracts it can cause a denial of service.&lt;/p&gt;
&lt;p&gt;This issue has been fixed in commit 3cd514031371d8aeeaf2048aa10103e02831aaa9&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;GNU cpio is vulnerable to an uncontrolled memory allocation in the make_path function at src/makepath.c. The function uses alloca to allocate stack memory based on the length of argpath, which is derived from an archive-controlled pathname during extraction. A malicious cpio archive containing a sufficiently long nested pathname causes an unbounded stack allocation, resulting in a stack overflow and crash of the cpio process. An attacker who can supply a crafted cpio archive to a victim who extracts it can cause a denial of service.&lt;/p&gt;
&lt;p&gt;This issue has been fixed in commit 3cd514031371d8aeeaf2048aa10103e02831aaa9&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-66485</guid>
    </item>
    <item>
      <title>GHSA-mmw4-f4p6-w77q</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-mmw4-f4p6-w77q</link>
      <description>&lt;p&gt;GNU cpio is vulnerable to an uncontrolled memory allocation in the make_path function at src/makepath.c. The function uses alloca to allocate stack memory based on the length of argpath, which is derived from an archive-controlled pathname during extraction. A malicious cpio archive containing a sufficiently long nested pathname causes an unbounded stack allocation, resulting in a stack overflow and crash of the cpio process. An attacker who can supply a crafted cpio archive to a victim who extracts it can cause a denial of service.&lt;/p&gt;
&lt;p&gt;This issue has been fixed in commit 3cd514031371d8aeeaf2048aa10103e02831aaa9&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;GNU cpio is vulnerable to an uncontrolled memory allocation in the make_path function at src/makepath.c. The function uses alloca to allocate stack memory based on the length of argpath, which is derived from an archive-controlled pathname during extraction. A malicious cpio archive containing a sufficiently long nested pathname causes an unbounded stack allocation, resulting in a stack overflow and crash of the cpio process. An attacker who can supply a crafted cpio archive to a victim who extracts it can cause a denial of service.&lt;/p&gt;
&lt;p&gt;This issue has been fixed in commit 3cd514031371d8aeeaf2048aa10103e02831aaa9&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-mmw4-f4p6-w77q</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-66485 — Uncontrolled Memory Allocation in GNU cpio</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-66485</link>
      <description>msrc_CVE-2026-66485</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-66485</guid>
    </item>
    <item>
      <title>OESA-2026-3456 — cpio security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-3456</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: cpio, openEuler:22.03-LTS-SP4: cpio, openEuler:24.03-LTS-SP1: cpio, openEuler:24.03-LTS-SP3: cpio, openEuler:24.03-LTS-SP4: cpio&lt;/p&gt;
&lt;p&gt;GNU cpio copies files into or out of a cpio or tar archive. The archive can be another file on the disk, a magnetic tape, or a pipe.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;GNU cpio contains a Path Traversal vulnerability in its tar archive extraction functionality. When extracting a tar archive in copy-in mode with the --no-absolute-filenames option, the extracted file name is normalized but the tar hard-link target is passed to the link_to_name function without equivalent sanitization before calling link function. A tar archive provided by an attacker, containing a hard-link entry whose linkname is set to an absolute path outside the extraction directory, can cause cpio to create a hard link to an existing file outside the intended extraction directory, breaking the expected guarantee of --no-absolute-filenames and allowing archive-controlled linkage to external files.&lt;/p&gt;
&lt;p&gt;This issue has been fixed in commit e2b9cbdd3354d2b1569b7390d1bc15c1930559ad(CVE-2026-66484)&lt;/p&gt;
&lt;p&gt;GNU cpio is vulnerable to an uncontrolled memory allocation in the make_path function at src/makepath.c. The function uses alloca to allocate stack memory based on the length of argpath, which is derived from an archive-controlled pathname during extraction. A malicious cpio archive containing a sufficiently long nested pathname causes an unbounded stack allocation, resulting in a stack overflow and crash of the cpio process. An attacker who can supply a crafted cpio archive to a victim who extracts it can cause a denial of service.…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: cpio, openEuler:22.03-LTS-SP4: cpio, openEuler:24.03-LTS-SP1: cpio, openEuler:24.03-LTS-SP3: cpio, openEuler:24.03-LTS-SP4: cpio&lt;/p&gt;
&lt;p&gt;GNU cpio copies files into or out of a cpio or tar archive. The archive can be another file on the disk, a magnetic tape, or a pipe.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;GNU cpio contains a Path Traversal vulnerability in its tar archive extraction functionality. When extracting a tar archive in copy-in mode with the --no-absolute-filenames option, the extracted file name is normalized but the tar hard-link target is passed to the link_to_name function without equivalent sanitization before calling link function. A tar archive provided by an attacker, containing a hard-link entry whose linkname is set to an absolute path outside the extraction directory, can cause cpio to create a hard link to an existing file outside the intended extraction directory, breaking the expected guarantee of --no-absolute-filenames and allowing archive-controlled linkage to external files.&lt;/p&gt;
&lt;p&gt;This issue has been fixed in commit e2b9cbdd3354d2b1569b7390d1bc15c1930559ad(CVE-2026-66484)&lt;/p&gt;
&lt;p&gt;GNU cpio is vulnerable to an uncontrolled memory allocation in the make_path function at src/makepath.c. The function uses alloca to allocate stack memory based on the length of argpath, which is derived from an archive-controlled pathname during extraction. A malicious cpio archive containing a sufficiently long nested pathname causes an unbounded stack allocation, resulting in a stack overflow and crash of the cpio process. An attacker who can supply a crafted cpio archive to a victim who extracts it can cause a denial of service.…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-3456</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11618-1 — cpio-2.15-8.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11618-1</link>
      <description>&lt;p&gt;cpio-2.15-8.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;cpio-2.15-8.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11618-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23355-1 — Security update for cpio</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:23355-1</link>
      <description>&lt;p&gt;Security update for cpio&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for cpio&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2026:23355-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-66485</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-66485</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: cpio, Ubuntu:Pro:16.04:LTS: cpio, Ubuntu:Pro:18.04:LTS: cpio, Ubuntu:Pro:20.04:LTS: cpio, Ubuntu:22.04:LTS: cpio, Ubuntu:24.04:LTS: cpio, Ubuntu:26.04:LTS: cpio&lt;/p&gt;
&lt;p&gt;GNU cpio is vulnerable to an uncontrolled memory allocation in the make_path function at src/makepath.c. The function uses alloca to allocate stack memory based on the length of argpath, which is derived from an archive-controlled pathname during extraction. A malicious cpio archive containing a sufficiently long nested pathname causes an unbounded stack allocation, resulting in a stack overflow and crash of the cpio process. An attacker who can supply a crafted cpio archive to a victim who extracts it can cause a denial of service. This issue has been fixed in commit 3cd514031371d8aeeaf2048aa10103e02831aaa9&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: cpio, Ubuntu:Pro:16.04:LTS: cpio, Ubuntu:Pro:18.04:LTS: cpio, Ubuntu:Pro:20.04:LTS: cpio, Ubuntu:22.04:LTS: cpio, Ubuntu:24.04:LTS: cpio, Ubuntu:26.04:LTS: cpio&lt;/p&gt;
&lt;p&gt;GNU cpio is vulnerable to an uncontrolled memory allocation in the make_path function at src/makepath.c. The function uses alloca to allocate stack memory based on the length of argpath, which is derived from an archive-controlled pathname during extraction. A malicious cpio archive containing a sufficiently long nested pathname causes an unbounded stack allocation, resulting in a stack overflow and crash of the cpio process. An attacker who can supply a crafted cpio archive to a victim who extracts it can cause a denial of service. This issue has been fixed in commit 3cd514031371d8aeeaf2048aa10103e02831aaa9&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-66485</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2722 — cpio: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2722</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in cpio ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial of Service zu verursachen oder Daten zu manipulieren.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in cpio ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial of Service zu verursachen oder Daten zu manipulieren.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2722</guid>
    </item>
  </channel>
</rss>
