Research

A Filename Spelling Trick Bypasses macOS Security Checks in Four Developer Tools, CERT/CC Warns

The filesystem and the security filter disagree about whether two names are the same file. Four developer tools shipped checks on the wrong side of that disagreement.

An aerial view of Apple Park, Apple’s headquarters in Cupertino, California.
Apple Park in Cupertino, California, Apple’s headquarters. The CERT/CC note is explicit that Apple itself is not the affected party: the flaws sit in third party tools whose filename checks disagree with APFS name resolution.

Photo: Daniel L. Lu, CC BY-SA 4.0, via Wikimedia Commons

Two filenames can be different strings and the same file. That mismatch sits at the center of a coordinated disclosure the CERT Coordination Center published on November 16, 2026, as vulnerability note VU#604762: on macOS, the Apple File System resolves some alternative Unicode spellings of a name to the same file on disk, while applications that compare paths as raw bytes treat the spellings as different files. A security check that rejects a protected path can therefore be shown a lookalike spelling, approve it, and watch the filesystem deliver the write to the protected target anyway. The note’s example pair is the German character ß and the letters ss.

CERT/CC, part of Carnegie Mellon University’s Software Engineering Institute, credits researcher Tomas Illuminati with reporting the issue; the note itself was written by Christopher Cullen. In the note’s words, affected tools can let local attackers “overwrite files anywhere the process has write permissions”, with data corruption, configuration hijacking and code execution among the possible outcomes. Four CVE identifiers were assigned during the coordination, and CERT/CC opened a fifth tracker, VU#604762.8, for the broader class.

The four assigned flaws

CVE-2026-45110, libarchive. The archive library behind many extraction tools carries both a file overwrite bypass and a directory exclusion bypass: a crafted archive entry whose name uses an alternative Unicode representation can slip past filename and directory exclusion checks, and because APFS resolves the entry to the real path, extraction can silently overwrite an existing file, with /etc/passwd given as the worked example.

CVE-2026-49401, Deno. The JavaScript and TypeScript runtime’s permission system compares a requested path against the values given to its deny flags for reading, writing, running and foreign function access using raw byte matching on macOS. A differently spelled version of a denied path could pass the comparison while APFS treats it as the same file. Deno’s own advisory lists versions up to 2.7.13 as affected and 2.7.14 as the patched release.

CVE-2026-59890, Python setuptools. Versions before 83.0.0 could be beaten the other way around: an NFD encoded filename could bypass an NFC exclusion rule written in a project’s MANIFEST.in file and end up included in a source distribution that its maintainers meant to keep it out of.

CVE-2026-14978, HashiCorp go-slug. The packaging component used by Terraform could let a file past .terraformignore exclusions through the same normalization mismatch, so sensitive files could be uploaded inside a Terraform slug that the exclusion rules were supposed to strip them from.

Apple Park in Cupertino, California, at sunset in June 2024.
Apple Park at sunset in June 2024. The affected software runs on macOS machines in development and build environments.

Photo: Nils Huenerfuerst, CC0, via Wikimedia Commons

The class is wider than four products

The fifth tracker, VU#604762.8, covers libraries that fail to lock colliding paths during parallel processing: when two spellings of one name are handled at the same time because the application sees two files and the filesystem sees one, a protected file can be overwritten in the race. CERT/CC lists 15 vendors and projects in the note. Apple is marked Not Affected, which matters for how the story is told: the flaw is not a bug assigned to macOS itself, but a disagreement between the filesystem’s longstanding name resolution behavior and checks written by the tools that run on it. Most other listed vendors, including Docker, Helm, IBM and Node.js, remain in Unknown status, which means their exposure has not been established either way. Apache Commons reviewed the report and rejected it as a vulnerability in Commons Compress. CERT/CC has reported no exploitation in the wild, and none of the four CVEs appears in CISA’s exploited vulnerabilities catalog.

What to do

Update the named tools first: Deno to 2.7.14, setuptools to 83.0.0 or later, and libarchive and go-slug to the releases their projects list in the note. The deeper fix belongs to tool authors rather than users: path checks have to compare names the way the filesystem resolves them, after normalization and case folding, not as raw bytes. Until the long tail of archive, packaging and build tools is audited, the practical defense for build pipelines is the boring one: extract and process untrusted archives with the least privilege available, so that a check that fails open lands in a directory the process was allowed to write anyway.

No corrections have been published for this article.

About the author

Devon Cross, Correspondent, beat: vulnerabilities & security research.