Skip to main content
VulnerabilityPublished Updated

CVE-2026-35372: uutils coreutils has a UNIX Symbolic Link (Symlink) Following issue

Affects coreutilsSource GCVE Database

0
Authoritative record:CVE-2026-35372· Medium 5.0

Not known to be exploited · CVSS 5.0 Medium : upgrade to 0.8.0 when convenient.

Data as of 27 Oct 2026, 00:27 UTC

CVSS 3.1 base score
5.0Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.8.0
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade coreutils to 0.8.0.

Affected software

ProductAffectedFixed in
crates.iocoreutilsAffected
  • <0.8.0
Fixed in
  • 0.8.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in uutils coreutils version 0.8.0 that fixes this issue. Users and administrators should upgrade to version 0.8.0 or later to remediate this vulnerability.

Description

A logic error in the ln utility of uutils coreutils causes it to dereference symbolic links even when the --no-dereference (-n) flag is used without --force. This leads to new links being created inside the target directory of the symlink rather than on the symlink itself. A local attacker could exploit this to redirect file creation into sensitive directories, potentially causing unauthorized file creation or system misconfiguration. The issue affects versions prior to 0.8.0 and has been fixed in version 0.8.0.

References

Community reviews

Loading reviews…