UBUNTU-CVE-2026-35345: Medium severity ubuntu/rust-coreutils vulnerability

Published Apr 22, 2026
·
Updated

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.

Affected Software

4 affected componentsFixes available
ubuntu/rust-coreutils*
ubuntu/rust-coreutils*
ubuntu/rust-coreutils<0.10.0-1ubuntu1
0.10.0-1ubuntu1
ubuntu/rust-coreutils*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade ubuntu/rust-coreutils to a version that resolves this vulnerability.

    Fixed in 0.10.0-1ubuntu1

Event History

Apr 22, 2026
CVE Published
via OSV·05:16 PM
Data Sourced
via OSV·05:16 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

Who is realistically exposed to this issue?

Systems are exposed when a privileged user monitors a log directory with uutils tail using --follow=name and a local attacker can write to that directory. The impact is disclosure of files readable by the privileged tail process.

2

What does an attacker need to exploit it?

The attacker needs local access with permission to replace a monitored log file in the relevant directory. They can replace that file with a symbolic link to a sensitive file, causing the privileged tail process to output the target's contents.

3

Is a default tail invocation affected?

The issue specifically involves the --follow=name option. The provided information does not establish that other tail modes or default invocations are affected.

4

What can be done if patching is not immediately possible?

Avoid using uutils tail with --follow=name as a privileged user on directories writable by less-privileged users. Restrict write access to directories containing files monitored by privileged processes.

5

How can I identify potentially affected usage?

Review privileged scripts, services, and interactive workflows for uutils tail commands using --follow=name. Prioritize cases where the monitored path is in a directory writable by local unprivileged users.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203