# CVE-2026-35372: uutils coreutils ln Security Bypass via Improper Handling of the --no-dereference Flag

> A logic error in uutils coreutils ln allows bypassing the no-dereference flag, enabling attackers to create files in sensitive directories via symlink manipulation.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 Apr 2026
- **Updated:** 22 Apr 2026
- **Also known as:** DEBIAN-CVE-2026-35372, GHSA-wq63-vh5h-pr5p, UBUNTU-CVE-2026-35372

## What is CVE-2026-35372?

CVE-2026-35372 is a medium-severity path traversal vulnerability in Uutils coreutils, published on 22 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-61 (UNIX Symbolic Link (Symlink) Following)

## Which versions are affected by CVE-2026-35372?

2 open source packages ship an affected version, including coreutils. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `coreutils` | crates.io | All versions | 0.8.0 |
| `coreutils` | crates.io | All versions | 0.8.0 |

Products: Uutils Coreutils.

## How do I fix CVE-2026-35372?

Upgrade coreutils to 0.8.0 or later.

## Is CVE-2026-35372 being exploited?

There is no known exploitation of CVE-2026-35372 in the wild and no public exploit code.

## Other vulnerabilities in Uutils coreutils

- [CVE-2026-35338](https://insights.sbomify.com/CVE-2026-35338/): uutils coreutils chmod Path Traversal Bypass of --preserve-root (high 7.3)
- [CVE-2026-35368](https://insights.sbomify.com/CVE-2026-35368/): uutils coreutils chroot Local Privilege Escalation and chroot Escape in via Name Service Switch (NSS) Injection (high 7.2)
- [CVE-2026-35341](https://insights.sbomify.com/CVE-2026-35341/): uutils coreutils mkfifo Unauthorized Permission Change on Existing Files (high 7.1)
- [CVE-2026-35352](https://insights.sbomify.com/CVE-2026-35352/): uutils coreutils mkfifo Privilege Escalation via TOCTOU Race Condition (high 7.0)
- [CVE-2026-35349](https://insights.sbomify.com/CVE-2026-35349/): uutils coreutils Path-Based Safety Bypass with --preserve-root (medium 6.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-35372 and fix it if it is affected.

What it is: CVE-2026-35372 is a medium-severity path traversal vulnerability in Uutils coreutils, published on 22 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-35372 in the wild and no public exploit code.

Affected packages and fixed versions:
- coreutils (crates.io): affected all versions; fixed in 0.8.0
- coreutils (crates.io): affected all versions; fixed in 0.8.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-35372/ (Markdown: https://insights.sbomify.com/CVE-2026-35372/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-35372
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-35372
- OSV: https://osv.dev/vulnerability/CVE-2026-35372

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-35372/
Summaries are generated and may contain mistakes; the official description above is the record.