In target-directory forms (`ln SOURCE... DIRECTORY`), `ln` rejects source paths with non-UTF-8 filename bytes, while GNU accepts them. Breaks GNU compatibility for byte-oriented filenames on Unix filesystems. PoC: ``` name=$(printf 'bad_\377'); mkdir dst; : > "$name"; ln "$name" dst # GNU: exit 0, creates dst/bad_\377 ; uutils: exit 1, dst empty ``` --- _Zellic private finding (zellic-ext/coreutils-private PR #84). Reported in the Zellic *uutils coreutils Program Security Assessment* (for Canonical, Jan 2026), audited commit `3a07ffc5a9bd4c283e75afa548ba1f1957bad242`._
Update uu_ln to 0.6.0 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanln: rejects non-UTF-8 source filenames in target-directory mode affects uu_ln (rust). Severity is low. In target-directory forms (`ln SOURCE... DIRECTORY`), `ln` rejects source paths with non-UTF-8 filename bytes, while GNU accepts them. Breaks GNU compatibility for byte-oriented filenames on Unix filesystems. PoC: ``` name=$(printf 'bad_\377'); mkdir dst; : > "$name"; ln "$name" dst # GNU: exit 0, creates dst/bad_\377 ; uutils: exit 1, dst empty ``` --- _Zellic private finding (zellic-ext/coreutils-private PR #84). Reported in the Zellic *uutils coreutils Program Security Assessment* (for Canonical, Jan 2026), audited commit `3a07ffc5a9bd4c283e75afa548ba1f1957bad242`._
AI coding agents often install or upgrade packages automatically in rust. A low vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| uu_lnrust | <0.6.0 |
In target-directory forms (`ln SOURCE... DIRECTORY`), `ln` rejects source paths with non-UTF-8 filename bytes, while GNU accepts them. Breaks GNU compatibility for byte-oriented filenames on Unix filesystems. PoC: ``` name=$(printf 'bad_\377'); mkdir dst; : > "$name"; ln "$name" dst # GNU: exit 0, creates dst/bad_\377 ; uutils: exit 1, dst empty ``` --- _Zellic private finding (zellic-ext/coreutils-private PR #84). Reported in the Zellic *uutils coreutils Program Security Assessment* (for Canonical, Jan 2026), audited commit `3a07ffc5a9bd4c283e75afa548ba1f1957bad242`._
Update uu_ln to 0.6.0 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanln: rejects non-UTF-8 source filenames in target-directory mode affects uu_ln (rust). Severity is low. In target-directory forms (`ln SOURCE... DIRECTORY`), `ln` rejects source paths with non-UTF-8 filename bytes, while GNU accepts them. Breaks GNU compatibility for byte-oriented filenames on Unix filesystems. PoC: ``` name=$(printf 'bad_\377'); mkdir dst; : > "$name"; ln "$name" dst # GNU: exit 0, creates dst/bad_\377 ; uutils: exit 1, dst empty ``` --- _Zellic private finding (zellic-ext/coreutils-private PR #84). Reported in the Zellic *uutils coreutils Program Security Assessment* (for Canonical, Jan 2026), audited commit `3a07ffc5a9bd4c283e75afa548ba1f1957bad242`._
AI coding agents often install or upgrade packages automatically in rust. A low vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| uu_lnrust | <0.6.0 |
| 0.6.0 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard| 0.6.0 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard