GBHackers reports macOS ß vs ss filename trick bypasses tool exclusions
GBHackers reports CERT/CC note VU#604762: a macOS ß vs ss path mismatch affects four tools; update setuptools to 83.0.0 or later.
- Published
- Fixed in
- setuptools 83.0.0 or later (per GBHackers); fixes for libarchive, go-slug and Deno not confirmed
- Exploitation
- Not confirmed. The GBHackers headline says hackers exploit the trick, but the article text gives no evidence of exploitation in the wild.
Live scores
CVE-2026-14978- EPSS
- 0.001
low predicted chance of attack - VEDAS
- 0.048
little exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Out of scope (local)
Live scores
CVE-2026-49401- EPSS
- 0.002
low predicted chance of attack - VEDAS
- 0.049
little exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Out of scope (local)
Live scores
CVE-2026-59890- EPSS
- 0.005
low predicted chance of attack - VEDAS
- 0.801
likely exploited - On CISA KEV
- Not listed
- Detection rule
- Out of scope (local)
What happened
According to GBHackers, CERT/CC published Vulnerability Note VU#604762 on November 16, 2026, describing a mismatch between the Apple File System (APFS) and the way several applications compare file paths GBHackers. GBHackers says an attacker can supply an alternative Unicode spelling, such as ß instead of ss, to get past security filters. We could not read the CERT/CC page itself (https://kb.cert.org/vuls/id/604762), so every detail below is as reported by GBHackers and has not been checked against the CERT/CC note.
GBHackers says the affected software enforces exclusion rules with byte-for-byte pathname comparisons, while APFS resolves different Unicode spellings of a name to the same file. In its account, a path that looks different to the filter can still point to a protected file, and a local attacker could overwrite any file the vulnerable process can write to. GBHackers lists data corruption, configuration hijacking or code execution as possible outcomes.
GBHackers reports four CVEs assigned during coordination:
- CVE-2026-45110: libarchive, where a crafted archive entry can be treated by APFS as /etc/passwd and overwrite it.
- CVE-2026-14978: HashiCorp go-slug, where .terraformignore exclusions can be bypassed so sensitive files end up in Terraform slug uploads.
- CVE-2026-49401: Deno, whose permission system, per GBHackers, compares requested paths with its deny-read, deny-write, deny-run and deny-ffi values using raw bytes on macOS.
- CVE-2026-59890: Python setuptools before version 83.0.0, where an NFD-encoded filename could bypass an NFC exclusion rule in MANIFEST.in and be included in a source distribution.
GBHackers also says a general tracker, VU#604762.8, covers libraries that do not properly lock colliding paths such as ß and ss, which could be processed in parallel.
The article says CERT/CC warns that backup tools, forensic workflows and CI/CD pipelines are exposed, and that a failed exclusion can leak sensitive files into distributed artifacts or corrupt build steps. It says Apple is listed as not affected for CVE-2026-45110, most of the 15 listed vendors remain in “Unknown” status, and Apache Commons rejected the report as a downstream issue.
Not confirmed: whether any of this has been exploited in the wild (the headline says hackers exploit it, but the article text gives no evidence), and fixed versions for libarchive, go-slug and Deno. Only one outlet carries this story, and it has not been independently verified.
Am I affected?
Per GBHackers, you may be affected if you use these on macOS:
- libarchive (CVE-2026-45110)
- HashiCorp go-slug (CVE-2026-14978)
- Deno with deny-style permission flags (CVE-2026-49401)
- Python setuptools before 83.0.0 (CVE-2026-59890)
GBHackers also names backup tools, forensic workflows and CI/CD pipelines that rely on path exclusion rules as exposed. It describes the file-overwrite scenario as one for a local attacker. Affected versions other than setuptools are not confirmed in the source, and most vendors are listed as “Unknown” status.
What to do now
- Update Python setuptools to 83.0.0 or later, as GBHackers advises GBHackers.
- Update libarchive, go-slug and Deno to their latest releases, as GBHackers advises. Which release fixes each issue is not confirmed, so check each project’s own advisory.
- Where you write your own path checks, validate paths using the filesystem’s own normalization rules instead of byte comparisons, as GBHackers advises.
- Review macOS build and backup jobs that depend on exclusion rules such as .terraformignore or MANIFEST.in, since GBHackers says a failed exclusion can leak files into artifacts.
- GBHackers says defenders should treat any unexpected file overwrite on macOS as a sign of possible compromise.