CVE-2026-35373: CWE-176: Improper Handling of Unicode Encoding in Uutils coreutils
A logic error in the ln utility of uutils coreutils causes the program to reject source paths containing non-UTF-8 filename bytes when using target-directory forms (e.g., ln SOURCE... DIRECTORY). While GNU ln treats filenames as raw bytes and creates the links correctly, the uutils implementation enforces UTF-8 encoding, resulting in a failure to stat the file and a non-zero exit code. In environments where automated scripts or system tasks process valid but non-UTF-8 filenames common on Unix filesystems, this divergence causes the utility to fail, leading to a local denial of service for those specific operations.
AI Analysis
Technical Summary
The vulnerability in uutils coreutils ln utility arises from improper handling of Unicode encoding (CWE-176). When using the target-directory form of ln, the utility enforces UTF-8 encoding on source paths, rejecting those with non-UTF-8 filename bytes. This contrasts with GNU ln, which accepts raw byte filenames and creates links correctly. As a result, uutils coreutils fails to stat files with non-UTF-8 names, returning a non-zero exit code and causing local denial of service in environments relying on such filenames. The CVSS score is 3.3 (low), indicating limited impact confined to availability on local systems. No patch or remediation level has been provided by the vendor, and no exploits are known.
Potential Impact
The impact is a local denial of service due to the ln utility failing to process source paths with non-UTF-8 filenames when using target-directory forms. This can disrupt automated scripts or system tasks that handle such filenames on Unix filesystems. There is no confidentiality or integrity impact reported. The issue affects availability locally and has a low severity rating. No known exploits exist in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should be aware of this limitation when using uutils coreutils ln with non-UTF-8 filenames and consider using GNU ln or alternative tools that handle raw byte filenames correctly to avoid failures.
CVE-2026-35373: CWE-176: Improper Handling of Unicode Encoding in Uutils coreutils
Description
A logic error in the ln utility of uutils coreutils causes the program to reject source paths containing non-UTF-8 filename bytes when using target-directory forms (e.g., ln SOURCE... DIRECTORY). While GNU ln treats filenames as raw bytes and creates the links correctly, the uutils implementation enforces UTF-8 encoding, resulting in a failure to stat the file and a non-zero exit code. In environments where automated scripts or system tasks process valid but non-UTF-8 filenames common on Unix filesystems, this divergence causes the utility to fail, leading to a local denial of service for those specific operations.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in uutils coreutils ln utility arises from improper handling of Unicode encoding (CWE-176). When using the target-directory form of ln, the utility enforces UTF-8 encoding on source paths, rejecting those with non-UTF-8 filename bytes. This contrasts with GNU ln, which accepts raw byte filenames and creates links correctly. As a result, uutils coreutils fails to stat files with non-UTF-8 names, returning a non-zero exit code and causing local denial of service in environments relying on such filenames. The CVSS score is 3.3 (low), indicating limited impact confined to availability on local systems. No patch or remediation level has been provided by the vendor, and no exploits are known.
Potential Impact
The impact is a local denial of service due to the ln utility failing to process source paths with non-UTF-8 filenames when using target-directory forms. This can disrupt automated scripts or system tasks that handle such filenames on Unix filesystems. There is no confidentiality or integrity impact reported. The issue affects availability locally and has a low severity rating. No known exploits exist in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should be aware of this limitation when using uutils coreutils ln with non-UTF-8 filenames and consider using GNU ln or alternative tools that handle raw byte filenames correctly to avoid failures.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- canonical
- Date Reserved
- 2026-04-02T12:58:56.088Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69e8f7d519fe3cd2cdd00d8e
Added to database: 4/22/2026, 4:31:17 PM
Last enriched: 4/22/2026, 4:47:43 PM
Last updated: 4/23/2026, 3:23:26 AM
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.