- Package:
- src:rust-coreutils
- Source:
- src:rust-coreutils
- Submitter:
- Moritz Mühlenhoff
- Date:
- 2026-08-07 09:31:03 UTC
- Severity:
- normal
- Tags:
Hi, The following vulnerability was published for rust-coreutils. CVE-2026-35345[0]: | A vulnerability in the tail utility of uutils coreutils allows for | the exfiltration of sensitive file contents when using the | --follow=name option. Unlike GNU tail, the uutils implementation | continues to monitor a path after it has been replaced by a symbolic | link, subsequently outputting the contents of the link's target. In | environments where a privileged user (e.g., root) monitors a log | directory, a local attacker with write access to that directory can | replace a log file with a symlink to a sensitive system file (such | as /etc/shadow), causing tail to disclose the contents of the | sensitive file. https://github.com/uutils/coreutils/issues/10328 If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2026-35345 https://www.cve.org/CVERecord?id=CVE-2026-35345 Please adjust the affected versions in the BTS as needed.
These CVEs are all fixed in the upstream 0.10.0 release, which was uploaded to unstable as rust-coreutils 0.10.0-1: #1135993 CVE-2026-35344 dd: propagate truncate errors on regular files #1135994 CVE-2026-35345 tail: treat a watched file replaced by a symlink as untailable #1136042 CVE-2026-35352 mkfifo: drop path-based chmod, closing the TOCTOU race #1136044 CVE-2026-35360 touch: create without O_TRUNC so a raced open no longer truncates #1136202 CVE-2026-35374 split: harden output open path against TOCTOU target swaps #1136203 CVE-2026-35376 chcon: anchor recursive relabel resolution to the traversal dirfd #1136207 CVE-2026-35377 env: keep backslashes literal in single quotes, matching GNU Cheers Sylvestre
Hi Sylvestre, It looks the fix for ttps://github.com/uutils/coreutils/issues/10328 did not reach though the 0.10.0 upstream version, can you check? Regards, Salvatore
Hi Salvatore, The fix did land in 0.10.0, just not via issue #10328, which wasn't closed: it went in as PR #12661 (commit 2c2f1b0c1, merged 2026-07-05, before the 0.10.0 tag). Cheers, Sylvestre Le 07/08/2026 à 05:49, Salvatore Bonaccorso a écrit :
Hi Sylvestre, Thanks, I will update our records accordingly. Regards, Salvatore
Impressive attention to details! :)-------- Original Message -------- On Friday, 08/07/26 at 09:53 Salvatore Bonaccorso <carnil@debian.org> wrote: Hi Sylvestre, Thanks, I will update our records accordingly. Regards, Salvatore