CVE-2026-75931
HIGHDescription
fast-uri is a URI parser for Node.js. It canonicalizes a host to its ASCII form only when the input carries an explicit scheme, so a scheme-relative reference such as a host preceded by two slashes is returned with its host verbatim and no error set. As a result fast-uri's own entry points disagree with each other: parse, resolve, normalize, and equal can yield different hosts for the same input depending only on whether a scheme is written out, and equal can return opposite verdicts for the same pair of hosts. An application that extracts a host with fast-uri to check it against a policy list and then resolves the same reference can make its decision on one host while the destination is another, enabling host confusion and policy bypass. The affected versions are 2.4.2 up to but not including 2.4.5, 3.1.3 up to but not including 3.1.6, and 4.0.1 up to but not including 4.1.3. The issue is fixed in 2.4.5, 3.1.6, and 4.1.3, which canonicalize the host consistently across the resolve path. Users should upgrade to a patched version.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 16% of all known CVEs.
References
Related Vulnerabilities
Other CWE-436 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2026-63030 | Critical | 9.8 | 97% | KEV | Fix |
| CVE-2025-25292 | Critical | 9.8 | 65% | - | Fix |
| CVE-2022-37436 | Medium | 5.3 | 58% | - | Fix |
| CVE-2021-28474 | High | 8.8 | 51% | - | Fix |
| CVE-2025-25291 | Critical | 9.8 | 20% | - | Fix |
| CVE-2019-17596 | High | 7.5 | 4.7% | - | Fix |
Common questions
How do I fix CVE-2026-75931?
No published fix for CVE-2026-75931 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-75931 being actively exploited?
Not that we know of. CVE-2026-75931 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.25% is the estimated probability that it will be exploited in the next 30 days. That is higher than 16% of all scored CVEs.
How severe is CVE-2026-75931?
CVE-2026-75931 has a CVSS v3 base score of 7.5, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-75931
Markdown
[](https://tridentstack.com/cve/CVE-2026-75931)HTML
<a href="https://tridentstack.com/cve/CVE-2026-75931"><img src="https://tridentstack.com/cve/badge/CVE-2026-75931.svg" alt="CVE-2026-75931"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-28.