<?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 sightings.</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent sightings.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 10 Oct 2026 14:57:12 +0000</lastBuildDate>
    <item>
      <title>6026b8cc-3c57-4412-820f-8c223f8b0de4</title>
      <link>https://vulnerability.circl.lu/sighting/6026b8cc-3c57-4412-820f-8c223f8b0de4/export</link>
      <description>{"uuid": "6026b8cc-3c57-4412-820f-8c223f8b0de4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-108119", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/117411991365542317", "content": "CVE-2026-108119 Busybox: busybox: tar extraction-root escape via deferred symlink/hardlink creation bypasses cve-2026-26158 fix A flaw was found in busybox. The tar applet's deferred link-creation handling for symlink and hardlink entries with unsafe-looking targets does not validate that the resolved destination remains inside the extraction directory once the deferred link is created. An attacker can craft a tar archive using a symlink target of exactly '..' combined with a deferred hardlink to create a new file outside the extraction directory, or reuse an extraction directory across two archives to replace an existing file outside it. If the archive is extracted with elevated privileges, this flaw can lead to privilege escalation or arbitrary code execution.\nhttps://www.cve.org/CVERecord?id=CVE-2026-108119https://access.redhat.com/security/cve/CVE-2026-108119https://bugzilla.redhat.com/show_bug.cgi?id=2548611#RedHat #RedHatEnterpriseLinux6 #RedHatHardenedImages#CVE_2026_108119#bot", "creation_timestamp": "2026-10-09T16:53:30.188946Z"}</description>
      <content:encoded>{"uuid": "6026b8cc-3c57-4412-820f-8c223f8b0de4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-108119", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/117411991365542317", "content": "CVE-2026-108119 Busybox: busybox: tar extraction-root escape via deferred symlink/hardlink creation bypasses cve-2026-26158 fix A flaw was found in busybox. The tar applet's deferred link-creation handling for symlink and hardlink entries with unsafe-looking targets does not validate that the resolved destination remains inside the extraction directory once the deferred link is created. An attacker can craft a tar archive using a symlink target of exactly '..' combined with a deferred hardlink to create a new file outside the extraction directory, or reuse an extraction directory across two archives to replace an existing file outside it. If the archive is extracted with elevated privileges, this flaw can lead to privilege escalation or arbitrary code execution.\nhttps://www.cve.org/CVERecord?id=CVE-2026-108119https://access.redhat.com/security/cve/CVE-2026-108119https://bugzilla.redhat.com/show_bug.cgi?id=2548611#RedHat #RedHatEnterpriseLinux6 #RedHatHardenedImages#CVE_2026_108119#bot", "creation_timestamp": "2026-10-09T16:53:30.188946Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/6026b8cc-3c57-4412-820f-8c223f8b0de4/export</guid>
      <pubDate>Fri, 09 Oct 2026 16:53:30 +0000</pubDate>
    </item>
  </channel>
</rss>
