← Voltar ao feed
medium technology

CERT/CC VU#604762: APFS Unicode normalization (ß vs ss) bypasses path exclusions in libarchive, go-slug, Deno and setuptools

1 fonte(s) · 1 atualização(ões) · publicado 17/11/2026 02:50 · coletado há 12 horas

CERT/CC published VU#604762 on November 16, 2026. It describes a mismatch between APFS Unicode path resolution and the byte-for-byte path comparisons used by several developer tools. An alternative Unicode spelling (for example ß instead of ss, or NFD instead of NFC) lets a path slip past exclusion rules while still resolving to the protected file. A local attacker can then overwrite files the vulnerable process can write to, or leak files that should have been excluded. This analysis rests on the article alone, because no web research was performed. The urgency is moderate because the flaw is local and affects macOS only.

Entenda a falha

A vulnerabilidade

CERT/CC VU#604762 describes a mismatch between APFS, which resolves different Unicode spellings of a name to the same file, and tools that compare paths byte for byte. An alternative spelling (ß vs ss, NFD vs NFC) passes exclusion rules but still reaches the protected file. A local attacker can overwrite any file the vulnerable process can write to, or cause excluded files to leak. CVE-2026-45110 (libarchive): a crafted archive entry can be treated by APFS as /etc/passwd and overwrite it. CVE-2026-14978 (HashiCorp go-slug): bypass of .terraformignore. CVE-2026-49401 (Deno): deny-read/write/run/ffi checks use raw bytes on macOS. CVE-2026-59890 (setuptools before 83.0.0): an NFD filename bypasses an NFC rule in MANIFEST.in. Fixed versions are only given for setuptools (83.0.0).

Como funciona

A path arrives from an archive entry, a project file tree or a permission request. The tool checks it against an exclusion or deny rule using a byte-for-byte comparison. Because the bytes differ from the excluded name, the check concludes the path is not covered and lets it through. The tool then opens or writes the path on APFS, which normalizes the Unicode spelling and resolves it to the protected file. The action therefore hits a file the rule was meant to exclude. Separately, libraries that do not lock colliding paths such as ß and ss may process them in parallel.

Por que é vulnerável

The root cause is a wrong assumption: the tools treat path identity as byte equality, while APFS treats differently encoded Unicode names as the same file. The security check and the filesystem therefore disagree on what a path is. The recommended fix is to validate paths with the filesystem's own normalization rules instead of byte comparisons. The articles do not describe the individual vendor patches beyond setuptools 83.0.0.

Onde está

The articles name no files or commits; they only mention the .terraformignore exclusions in go-slug, the --deny-read/--deny-write/--deny-run/--deny-ffi values in Deno and the exclusion rules in MANIFEST.in in setuptools.

Como foi descoberta

The articles do not say who found the flaw or how. They say CERT/CC published VU#604762 on November 16, 2026, after four CVEs were assigned during coordination. Of the 15 vendors listed, most have an Unknown status, Apple is listed as not affected for CVE-2026-45110, and Apache Commons rejected the report as a downstream issue.

Explicação gerada por IA a partir da matéria e dos artigos, em 17/11/2026 04:16.

Detalhes técnicos

  • CVE-2026-45110 (libarchive): a crafted archive entry can be treated by APFS as /etc/passwd and overwrite it.
  • CVE-2026-14978 (HashiCorp go-slug): bypasses .terraformignore, so sensitive files end up in Terraform slug uploads.
  • CVE-2026-49401 (Deno): the permission system compares paths against the --deny-read, --deny-write, --deny-run and --deny-ffi values as raw bytes on macOS.
  • CVE-2026-59890 (setuptools before 83.0.0): an NFD-encoded filename bypasses an NFC exclusion rule in MANIFEST.in and is included in a source distribution.
  • Tracker VU#604762.8 covers libraries that do not lock colliding paths such as ß and ss, which can then be processed in parallel.
  • Backup tools, forensic workflows and CI/CD pipelines are exposed. A failed exclusion can leak sensitive files into artifacts or corrupt build steps.
  • Apple is listed as not affected for CVE-2026-45110. Most of the 15 listed vendors have "Unknown" status. Apache Commons rejected the report as a downstream issue.

Remediação

  • Update to the latest releases, including setuptools 83.0.0 or later.
  • Validate paths with the filesystem's own normalization rules rather than byte comparisons.
  • Treat unexpected file overwrites on macOS as a possible compromise.

Linha do tempo

  1. gbhackers.com ↗ · pub. 17/11/2026 02:50 · coletado 17/11 04:00 primeiro registro

    CERT/CC VU#604762: APFS Unicode normalization (ß vs ss) bypasses path exclusions in libarchive, go-slug, Deno and setuptools

    ler a análise desta fonte

    CERT/CC published VU#604762 on November 16, 2026. It describes a mismatch between APFS Unicode path resolution and the byte-for-byte path comparisons used by several developer tools. An alternative Unicode spelling (for example ß instead of ss, or NFD instead of NFC) lets a path slip past exclusion rules while still resolving to the protected file. A local attacker can then overwrite files the vulnerable process can write to, or leak files that should have been excluded. This analysis rests on the article alone, because no web research was performed. The urgency is moderate because the flaw is local and affects macOS only.

    Technical Details

    • CVE-2026-45110 (libarchive): a crafted archive entry can be treated by APFS as /etc/passwd and overwrite it.
    • CVE-2026-14978 (HashiCorp go-slug): bypasses .terraformignore, so sensitive files end up in Terraform slug uploads.
    • CVE-2026-49401 (Deno): the permission system compares paths against the --deny-read, --deny-write, --deny-run and --deny-ffi values as raw bytes on macOS.
    • CVE-2026-59890 (setuptools before 83.0.0): an NFD-encoded filename bypasses an NFC exclusion rule in MANIFEST.in and is included in a source distribution.
    • Tracker VU#604762.8 covers libraries that do not lock colliding paths such as ß and ss, which can then be processed in parallel.
    • Backup tools, forensic workflows and CI/CD pipelines are exposed. A failed exclusion can leak sensitive files into artifacts or corrupt build steps.
    • Apple is listed as not affected for CVE-2026-45110. Most of the 15 listed vendors have "Unknown" status. Apache Commons rejected the report as a downstream issue.

    Remediation

    • Update to the latest releases, including setuptools 83.0.0 or later.
    • Validate paths with the filesystem's own normalization rules rather than byte comparisons.
    • Treat unexpected file overwrites on macOS as a possible compromise.