CVE-2026-35372 json
uutils coreutils ln Security Bypass via Improper Handling of the --no-dereference Flag
published 6mo ago modified 14d ago also GHSA-wq63-vh5h-pr5p , EUVD-2026-25020
- cvss
- 5.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 3%
- public exploits
- 0
- none known
Summary
A logic error in the ln utility of uutils coreutils allows the utility to dereference a symbolic link target even when the --no-dereference (or -n) flag is explicitly provided. The implementation previously only honored the "no-dereference" intent if the --force (overwrite) mode was also enabled. This flaw causes ln to follow a symbolic link that points to a directory and create new links inside that target directory instead of treating the symbolic link itself as the destination. In environments where a privileged user or system script uses ln -n to update a symlink, a local attacker could manipulate existing symbolic links to redirect file creation into sensitive directories, potentially leading to unauthorized file creation or system misconfiguration.
Patch / fix
- crates.io coreutils 0.8.0
- Uutils coreutils 0.8.0
- rust-coreutils Debian 14 0.8.0-1
debian advisories DEBIAN-CVE-2026-35372
- github.com/uutils/coreutils@394c4b1 commit
- github.com/uutils/coreutils#11253 pull request
- github.com/uutils/coreutils/releases/tag/0.8.0 release
Is CVE-2026-35372 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-35372 updated cvss 5.0
rust-coreutils: ln: security bypass via improper handling of the --no-dereference flag
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 6mo ago
Exploit prediction
0.14% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.0 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N |
| GitHub | 3.1 | 5.0 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | coreutils | <0.8.0 |
0.8.0 |
Affected products
- Uutils coreutils
Classification
- Weakness
-
- CWE-61 UNIX Symbolic Link (Symlink) Following
References
-
github.com
/uutils/coreutils/pull/11253
issue-tracking, patch, web
-
github.com
/uutils/coreutils/commit/394c4b17f2f382b4be9f54389bcb79028de02f39
web
-
github.com
/uutils/coreutils/releases/tag/0.8.0
vendor-advisory, web, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2026-35372
advisory
-
github.com
/uutils/coreutils
package
Sources
- CVE List CVE-2026-35372
- GitHub Advisory GHSA-wq63-vh5h-pr5p
- NVD CVE-2026-35372
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.