A significant security flaw involving Unicode normalization has been identified, impacting macOS systems by allowing attackers to bypass file exclusion checks. This vulnerability affects several developer tools, including Deno, libarchive, HashiCorp’s go-slug, and Python’s setuptools, across four CVEs.
Understanding the Unicode Normalization Issue
This flaw originates from discrepancies in how different system components interpret file names. Apple’s File System (APFS) resolves paths considering various Unicode spellings as referring to the same file, whereas affected tools make comparisons using raw byte data. This leads to an inconsistency where the byte-level comparison sees “ß” and “ss” as distinct, while APFS treats them as identical.
Exploiters can leverage this inconsistency by providing a file path that bypasses exclusion rules. Once bypassed, APFS resolves the path to the intended protected file, allowing unauthorized access.
Specific Vulnerabilities and Implications
CVE-2026-45110 impacts libarchive and includes a file-overwrite and directory-exclusion bypass. Attackers can insert similarly named files, like variations of “password,” into an archive, which APFS might interpret as critical files like /etc/passwd, leading to silent overwrites.
For Deno, CVE-2026-49401 affects the permission system’s path checks, which use raw-byte matching. Variations in Unicode spelling that APFS treats uniformly can bypass these checks, compromising security.
CVE-2026-14978 targets HashiCorp go-slug, where improper handling of Unicode normalization allows attackers to bypass .terraformignore rules, potentially exposing sensitive files in Terraform uploads.
Recommendations and Preventative Measures
The vulnerability in setuptools, CVE-2026-59890, was addressed in version 83.0.0. It involved improper application of MANIFEST.in directives against file names. Updates have been made to correct these normalization issues.
CERT/CC has highlighted related issues in VU#604762.8, addressing problems with case-insensitive or normalization-insensitive file systems. In such scenarios, conflicting paths like ß and ss may be processed simultaneously, creating a risk of protected file overwrites.
Developers and security teams are urged to update affected software to the latest versions and avoid using raw byte comparisons for path checks. Normalizing paths to match operating system standards can prevent such vulnerabilities.
Future Outlook and Security Advice
This flaw underscores the critical need for robust handling of Unicode in security systems. CERT/CC advises careful monitoring of tools that manipulate files on macOS build hosts, ensuring unexpected file writes are promptly identified and addressed. While no known exploitation has occurred in the wild, vigilance is essential.
Organizations should integrate threat intelligence to stay ahead of potential incidents, ensuring that their security operations centers (SOCs) remain informed about the latest threats and vulnerabilities.
