Quick answers
- Is CVE-2026-35373 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-35373 being exploited in the wild.
- How severe is CVE-2026-35373?
- Low severity, with a CVSS score of 3.3, published 22 April 2026.
- Which products and versions are affected?
- uu_ln (crates.io) < 0.6.0, SEMVER:introduced=0,fixed=0.6.0.
- Is there a fix for CVE-2026-35373?
- Yes. uu_ln (crates.io): upgrade to 0.6.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-35373 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-35373?
- Check whether you run uu_ln (crates.io) or Uutils Coreutils at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- uu_ln (crates.io): upgrade to 0.6.0 or later
cargo update -p uu_ln
Technical details
A logic error in the 'ln' utility (uu_ln) of uutils coreutils causes the program to enforce UTF-8 encoding on source paths when using target-directory forms (e.g., 'ln SOURCE... DIRECTORY'). This deviates from GNU behavior, which treats filenames as raw bytes. An attacker or a system environment with filenames containing non-UTF-8 bytes (such as 0xFF) will cause the utility to fail to 'stat' the file, resulting in a non-zero exit code and failure to create the link. This is classified as CWE-176 (Improper Handling of Unicode Encoding). The issue is fixed in version 0.6.0.
Affected products
- uutils coreutils uu_ln < 0.6.0
Identifiers
- CVE-2026-35373
- GHSA-jcjr-rh8q-7xqf
Timeline
- 2026-01-01: disclosed: Reported in Zellic uutils coreutils Program Security Assessment
- 2026-03-18: other: Pull request 11403 opened to fix the issue
- 2026-05-30: patched: Version 0.6.0 released with fix
- 2026-07-06: advisory: GitHub Advisory published