# CVE-2026-93751: uri-js through 4.4.1 Improper UTF-8 Decoding via pctDecChars

> Attackers can bypass validation to inject path traversal or CRLF sequences via improper UTF-8 decoding in the uri-js library.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** AZL-103436, DEBIAN-CVE-2026-93751, GHSA-7g43-p94j-qr58, UBUNTU-CVE-2026-93751

## What is CVE-2026-93751?

CVE-2026-93751 is a medium-severity path traversal vulnerability in garycourt uri-js, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

uri-js through 4.4.1 contains an improper UTF-8 decoding vulnerability in pctDecChars() that decodes invalid and overlong percent-encoded sequences into ASCII metacharacters. Attackers can craft percent-encoded payloads to bypass platform decoder validation and inject path traversal or CRLF sequences that downstream consumers process without filtering.

Weakness: CWE-176 (Improper Handling of Unicode Encoding)

## Which versions are affected by CVE-2026-93751?


## How do I fix CVE-2026-93751?

No fix has been published for CVE-2026-93751 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-93751 being exploited?

There is no known exploitation of CVE-2026-93751 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93751 and fix it if it is affected.

What it is: CVE-2026-93751 is a medium-severity path traversal vulnerability in garycourt uri-js, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93751 in the wild and no public exploit code.

Affected product: garycourt uri-js. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93751/ (Markdown: https://insights.sbomify.com/CVE-2026-93751/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93751
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93751
- OSV: https://osv.dev/vulnerability/CVE-2026-93751

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93751/
Summaries are generated and may contain mistakes; the official description above is the record.