Path traversal and CRLF injection via malformed UTF-8
Published Sep 18, 2026 · Updated Sep 18, 2026
Improper UTF-8 decoding in URI.js 4.4.1 and earlier allows remote attackers to inject path traversal or CRLF sequences. The pctDecChars() decoder masks bytes without validating continuation bytes or rejecting overlong encodings, turning malformed percent encodings into ASCII metacharacters. Exploitation requires an application to validate untrusted URI data with a standard decoder, then process it with unescapeComponent or parse and trust the second decoded value in a path or downstream protocol.
Summary
What happened
Improper UTF-8 decoding in URI.js 4.4.1 and earlier allows remote attackers to inject path traversal or CRLF sequences. The pctDecChars() decoder masks bytes without validating continuation bytes or rejecting overlong encodings, turning malformed percent encodings into ASCII metacharacters. Exploitation requires an application to validate untrusted URI data with a standard decoder, then process it with unescapeComponent or parse and trust the second decoded value in a path or downstream protocol.
The record
- CVE
- CVE-2026-93751
- Published
- Sep 18, 2026
- Updated
- Sep 18, 2026
- Vendor
- Gary Court
- Product
- URI.js
- Classifications
- CWE-176
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 18, 2026CVE publishedPublication date reported by the CVE source.
- Sep 18, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=4.4.1
What conditions does exploitation require?
What is affected?
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- GitHub Issue #106 reproduction payloadsproof 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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started