<?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://db.gcve.eu</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>Sat, 03 Oct 2026 17:01:11 +0000</lastBuildDate>
    <item>
      <title>GHSA-r6q2-hw4h-h46w — Race Condition in node-tar Path Reservations via Unicode Ligature Collisions on macOS APFS</title>
      <link>https://db.gcve.eu/vuln/ghsa-r6q2-hw4h-h46w</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: tar&lt;/p&gt;
&lt;p&gt;**TITLE**: Race Condition in node-tar Path Reservations via Unicode Sharp-S (ß) Collisions on macOS APFS&lt;/p&gt;
&lt;p&gt;**AUTHOR**: Tomás Illuminati&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;A race condition vulnerability exists in `node-tar` (v7.5.3) this is to an incomplete handling of Unicode path collisions in the `path-reservations` system. On case-insensitive or normalization-insensitive filesystems (such as macOS APFS, In which it has been tested), the library fails to lock colliding paths (e.g., `ß` and `ss`), allowing them to be processed in parallel. This bypasses the library&amp;#39;s internal concurrency safeguards and permits Symlink Poisoning attacks via race conditions. The library uses a `PathReservations` system to ensure that metadata checks and file operations for the same path are serialized. This prevents race conditions where one entry might clobber another concurrently.&lt;/p&gt;
&lt;p&gt;```typescript
// node-tar/src/path-reservations.ts (Lines 53-62)
reserve(paths: string[], fn: Handler) {
    paths =
      isWindows ?
        [&amp;#39;win32 parallelization disabled&amp;#39;]
      : paths.map(p =&amp;gt; {
          return stripTrailingSlashes(
            join(normalizeUnicode(p)), // &amp;lt;- THE PROBLEM FOR MacOS FS
          ).toLowerCase()
        })&lt;/p&gt;
&lt;p&gt;```&lt;/p&gt;
&lt;p&gt;In MacOS the ```join(normalizeUnicode(p)), ``` FS confuses ß with ss, but this code does not. For example:&lt;/p&gt;
&lt;p&gt;``````bash
bash-3.2$ printf &amp;#34;CONTENT_SS\n&amp;#34; &amp;gt; collision_test_ss
bash-3.2$ ls
collision_test_ss
bash-3.2$ printf &amp;#34;CONTENT_ESSZETT\n&amp;#34; &amp;gt; collision_test_ß
bash-3.2$ ls -la
total 8
drwx…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: tar&lt;/p&gt;
&lt;p&gt;**TITLE**: Race Condition in node-tar Path Reservations via Unicode Sharp-S (ß) Collisions on macOS APFS&lt;/p&gt;
&lt;p&gt;**AUTHOR**: Tomás Illuminati&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;A race condition vulnerability exists in `node-tar` (v7.5.3) this is to an incomplete handling of Unicode path collisions in the `path-reservations` system. On case-insensitive or normalization-insensitive filesystems (such as macOS APFS, In which it has been tested), the library fails to lock colliding paths (e.g., `ß` and `ss`), allowing them to be processed in parallel. This bypasses the library&amp;#39;s internal concurrency safeguards and permits Symlink Poisoning attacks via race conditions. The library uses a `PathReservations` system to ensure that metadata checks and file operations for the same path are serialized. This prevents race conditions where one entry might clobber another concurrently.&lt;/p&gt;
&lt;p&gt;```typescript
// node-tar/src/path-reservations.ts (Lines 53-62)
reserve(paths: string[], fn: Handler) {
    paths =
      isWindows ?
        [&amp;#39;win32 parallelization disabled&amp;#39;]
      : paths.map(p =&amp;gt; {
          return stripTrailingSlashes(
            join(normalizeUnicode(p)), // &amp;lt;- THE PROBLEM FOR MacOS FS
          ).toLowerCase()
        })&lt;/p&gt;
&lt;p&gt;```&lt;/p&gt;
&lt;p&gt;In MacOS the ```join(normalizeUnicode(p)), ``` FS confuses ß with ss, but this code does not. For example:&lt;/p&gt;
&lt;p&gt;``````bash
bash-3.2$ printf &amp;#34;CONTENT_SS\n&amp;#34; &amp;gt; collision_test_ss
bash-3.2$ ls
collision_test_ss
bash-3.2$ printf &amp;#34;CONTENT_ESSZETT\n&amp;#34; &amp;gt; collision_test_ß
bash-3.2$ ls -la
total 8
drwx…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-r6q2-hw4h-h46w</guid>
    </item>
  </channel>
</rss>
