CERT/CC Warns of Unicode Normalization Collision on macOS APFS Affecting Deno, libarchive, setuptools and HashiCorp
Multiple vendors issued patches for a filesystem-level flaw where APFS treats different Unicode spellings as the same file, allowing attackers to bypass exclusion filters and overwrite protected files.

By TechWhoKnows
, updated 3 min read
The CERT Coordination Centre has published vulnerability note VU#604762 detailing a class of flaws affecting multiple vendors on macOS where Apple File System (APFS) Unicode normalization behaviour diverges from application-level path comparisons, allowing local attackers to bypass security exclusions and overwrite protected files.
The core issue
APFS treats different Unicode spellings of the same name as the same file, for example, the German sharp S (ß) and the double-s (ss) sequence resolve to the same filesystem entry. However, multiple applications enforce exclusion filters or path locks using byte-for-byte pathname comparisons that do not account for this normalization. By supplying an alternative Unicode spelling, an attacker can bypass the application's checks while the filesystem silently overwrites the target file.
Four CVEs assigned across widely-used tools
CVE | Component | Impact |
|---|---|---|
CVE-2026-45110 | libarchive | File overwrite bypass and directory exclusion bypass; attacker can add a file like |
CVE-2026-49401 | Deno | Permission system (--deny-read, --deny-write, --deny-run, --deny-ffi) used raw-byte pathname matching while APFS treats Unicode variants as identical |
CVE-2026-59890 | setuptools (pre-83.0.0) | FileList applied MANIFEST.in exclude directives without Unicode normalization; NFD filenames could bypass NFC exclusion rules and be packed into source distributions |
CVE-2026-14978 | HashiCorp go-slug | Could allow bypassing |
Additional affected vendors
The vulnerability note lists 15 vendors notified, including Apache Commons, Docker, Helm, IBM, Node.js, npm (ignore-walk), Pulumi, Python (flit), and Yarn. Several have unknown status as of the 16 November 2026 publication date.
Supply chain and CI/CD risk
The flaw extends beyond local file overwrite. Supply chain workflows are exposed where failure to correctly exclude items can result in inadvertent inclusion of sensitive files in distributed artifacts or corruption of CI/CD build steps. Backup tools and forensic workflows using affected libraries are also at risk.
Remediation
CERT/CC recommends updating affected software to the latest versions. Developers should implement path validation that accounts for the underlying filesystem's normalization behaviour rather than relying on byte-for-byte comparisons. All security filters should use path formats matching the resolution logic used by the operating system.
The vulnerability was reported by Tomas Illuminati, a cyber security researcher and threat intelligence analyst. CERT/CC acknowledges the maintainers of the various projects who acted quickly to resolve these issues.
Sources
- 1CERT/CC Vulnerability Note VU#604762kb.cert.org