Local service interruption via UTF-8 path rejection
Published Apr 22, 2026 · Updated Apr 22, 2026
Improper Unicode handling in uutils coreutils before 0.6.0 allows local users to interrupt ln target-directory operations. The ln target-directory path handling enforces UTF-8 on source filename bytes, then fails to stat valid Unix paths containing non-UTF-8 bytes. The failure requires a local user or automated task to supply such a filename and is limited to a nonzero exit without link creation.
Summary
What happened
Improper Unicode handling in uutils coreutils before 0.6.0 allows local users to interrupt ln target-directory operations. The ln target-directory path handling enforces UTF-8 on source filename bytes, then fails to stat valid Unix paths containing non-UTF-8 bytes. The failure requires a local user or automated task to supply such a filename and is limited to a nonzero exit without link creation.
The record
- CVE
- CVE-2026-35373
- Published
- Apr 22, 2026
- Updated
- Apr 22, 2026
- Vendor
- uutils
- Product
- coreutils
- Classifications
- CWE-176
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 22, 2026CVE publishedPublication date reported by the CVE source.
- Apr 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream non-UTF-8 filename reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo