Duplicate Advisory: uutils coreutils has an Improper Handling of Unicode Encoding Issue
### Duplicate Advisory This advisory has been withdrawn because it is a duplicate of GHSA-jcjr-rh8q-7xqf. This link is maintained to preserve external references. ### Original 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 Analysis
Technical Summary
The vulnerability in uutils coreutils ln utility arises from improper handling of Unicode encoding. When source paths contain non-UTF-8 filename bytes, the utility rejects them instead of processing as GNU ln does. This behavior leads to failure in creating links and a non-zero exit code, causing local denial of service in environments using valid but non-UTF-8 filenames. This issue affects versions up to and including 0.8.0.
Potential Impact
The impact is a local denial of service due to the utility failing to process valid filenames containing non-UTF-8 bytes. There is no confidentiality or integrity impact reported. The failure affects automated scripts or system tasks relying on uutils coreutils ln to handle such filenames correctly.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Users should monitor vendor communications for updates or fixes addressing this logic error. Until a fix is available, consider using GNU ln or avoiding non-UTF-8 filenames in affected environments.
Duplicate Advisory: uutils coreutils has an Improper Handling of Unicode Encoding Issue
Description
### Duplicate Advisory This advisory has been withdrawn because it is a duplicate of GHSA-jcjr-rh8q-7xqf. This link is maintained to preserve external references. ### Original 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.
CVSS v3.1
Score 3.3low
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in uutils coreutils ln utility arises from improper handling of Unicode encoding. When source paths contain non-UTF-8 filename bytes, the utility rejects them instead of processing as GNU ln does. This behavior leads to failure in creating links and a non-zero exit code, causing local denial of service in environments using valid but non-UTF-8 filenames. This issue affects versions up to and including 0.8.0.
Potential Impact
The impact is a local denial of service due to the utility failing to process valid filenames containing non-UTF-8 bytes. There is no confidentiality or integrity impact reported. The failure affects automated scripts or system tasks relying on uutils coreutils ln to handle such filenames correctly.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Users should monitor vendor communications for updates or fixes addressing this logic error. Until a fix is available, consider using GNU ln or avoiding non-UTF-8 filenames in affected environments.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-xh5h-p8c5-4w4x
- Osv Schema Version
- 1.4.0
- Aliases
- []
- Ecosystems
- ["crates.io"]
- Database Specific Severity
- LOW
- Cvss Version
- 3.1
Threat ID: 6a4c341a27e9c797195f8428
Added to database: 07/06/2026, 23:02:50 UTC
Last enriched: 07/07/2026, 00:22:18 UTC
Last updated: 07/31/2026, 12:27:13 UTC
Views: 43
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.