Skip to content
nulltapE-reader edition

← All e-reader articles

5 min read

macOS File Collisions Let Build Tools Include Excluded Files

CERT/CC links Unicode pathname collisions on macOS to exclusions bypassed in source packages and Terraform uploads, plus file overwrites in extraction workflows.

Read on the standard site

Close crop of a large blue file folder on the screen of a silver Mac laptop.

A filename that a macOS build job thinks it excluded can still land in a source archive or Terraform upload. CERT/CC’s November 16 coordinated note connects that failure to Unicode pathname collisions in setuptools and HashiCorp go-slug, alongside permission bypasses in Deno and extraction overwrites in libarchive. Teams building or unpacking untrusted projects on affected macOS filesystems should inspect the resulting artifacts for files their exclusion rules were meant to keep out.

A filter compares two spellings as different strings; APFS can resolve them to the same file. CERT/CC credits researcher Tomas Illuminati and says the mismatch lets an attacker bypass exclusions using “alternative Unicode spellings.” The consequence depends on the tool: a secret can enter a distributed package, or a file can be overwritten within the process’s write permissions. The attacker needs a pathname they can place in a local directory or in material consumed by the job.

Two spellings reach one file

Apple’s APFS guide says APFS preserves a filename’s original form while finding it through normalization variants. Apple describes case-insensitive APFS as the default on macOS; the archived guide also describes normalization-insensitive matching in its case-sensitive variant. The failure comes when a security check compares raw pathname bytes, then an operation opens or packages the filesystem-resolved file.

Think of a guest list that checks names as printed on the invitation, while the front desk recognizes two spellings as the same guest. The list and the desk each do their assigned job, but the exclusion never reaches the file the desk hands over. CERT/CC also describes a case-folding collision such as ß and ss; the precise equivalence depends on the volume and the path operation. A developer must test the security comparison against the actual filesystem resolution for the volume and operation in use.

Package filters admit unwanted files

For Python source distributions, the CVE-2026-59890 record says setuptools FileList applied MANIFEST.in rules against on-disk names without normalization. Before 83.0.0, an NFD name could slip past an NFC-form exclusion on macOS APFS or HFS+ and enter the built distribution. The named directives are exclude, global-exclude, recursive-exclude and prune. If that distribution is uploaded, its contents travel beyond the build machine.

HashiCorp go-slug has a related upload path. The CVE-2026-14978 record identifies versions 0.4.0 through 0.18.2: a local attacker can evade .terraformignore and cause sensitive files to enter Terraform slug uploads. IBM’s assigned record advises evaluating the risk and upgrading to v0.18.3. Inventory the version actually used by the upload job, including pinned build dependencies, and inspect the upload input for files the ignore rule was meant to exclude.

Read the source distribution or upload bundle to see which files the job included. Where a build accepts files from collaborators or automation, inspect the generated archive listing and compare its actual members with the intended exclusions, including names equivalent under the target filesystem’s matching behavior. Remove sensitive material from the build context when it has no reason to be there.

Deno denies the wrong spelling

The Deno CVE-2026-49401 record describes a different consequence of the same mismatch. Before 2.7.14, Deno compared the path requested by a program with the raw path in --deny-read, --deny-write, --deny-run or --deny-ffi. On affected macOS APFS volumes, a differently spelled request could resolve to a path that the deny rule was meant to block. Upgrade Deno jobs that rely on those restrictions to 2.7.14 or later, then verify the installed runtime and the deny flags in the actual job configuration.

CERT/CC assigns CVE-2026-45110 to libarchive’s file-overwrite and directory-exclusion bypass during archive extraction. A crafted colliding name can reach a protected destination when extraction runs with write permission there. Apply your distributor’s applicable libarchive update, keep extraction in a directory with only the write permissions it needs, and inspect the resulting tree for unexpected files before using it as a build input. Treat a matching file as a reason to examine its origin and the extraction job’s permissions.

The coordinated note lists several vendor statuses as unknown. It also records that Apache Commons rejects the issue as a Commons Compress vulnerability, pointing instead to downstream code that creates symlinks and validates paths without checking their targets. Apple is listed as not affected. Start triage with the named vulnerable code paths and the software your jobs actually use.

Inspect the artifact after filtering

On macOS builders, record the filesystem variant and the versions used by the job. Move setuptools builds to 83.0.0 or later, HashiCorp go-slug uploads to v0.18.3 or later after the risk review in its CVE record, and Deno restrictions to 2.7.14 or later. For libarchive, use the applicable distributor fix and limit extraction write access. For your own filter code, compare paths with the volume’s resolution behavior and reject collisions before opening or packaging a file, as CERT/CC recommends.

Run a verification on a disposable, non-sensitive test project that contains a filename variant covered by your exclusion policy. Inspect the produced source distribution or upload bundle: the excluded member should be absent. Check the extraction output tree and the process’s write scope when archive handling is involved. The check must use the same macOS volume type, tool build and exclusion settings as the job it represents; a test on a different filesystem can miss this failure.

Keep the artifact listing alongside the job’s dependency versions. A later reviewer can then identify the specific files that left the build machine.

Primary sources