<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-28T23:33:26.982273+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-29786</id>
    <title>CVE-2026-29786 — node-tar: Hardlink Path Traversal via Drive-Relative Linkpath</title>
    <updated>2026-09-28T23:33:26.983973+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> isaacs node-tar, Red Hat Cryostat 4, Red Hat Logging Subsystem for Red Hat OpenShift, Red Hat Network Observability Operator, Red Hat 3scale API Management Platform 2, Red Hat Advanced Cluster Management for Kubernetes 2, Red Hat AMQ Broker 7, Red Hat build of Apache Camel - HawtIO 4, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8 and 12 more</p>
<p>node-tar is a full-featured Tar for Node.js. Prior to version 7.5.10, tar can be tricked into creating a hardlink that points outside the extraction directory by using a drive-relative link target such as C:../target.txt, which enables file overwrite outside cwd during normal tar.x() extraction. This issue has been patched in version 7.5.10.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-29786"/>
  </entry>
</feed>
