Security Resilience

CVE-2026-18446

Openjsf Fast-Uri ≤ 2.4.4

Published
31 July 2026
Modified
02 September 2026
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS Score 0.0038 32th percentile
Risk Priority 57 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-18446 is a high-severity Interpretation Conflict (CWE-436) vulnerability in Openjsf Fast-Uri. Its CVSS base score is 7.5 (High).

Operationally, ranked at the 32th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

fast-uri before 4.1.2, 3.1.5, and 2.4.4 requires a literal double forward slash to recognize a URI authority, so a reference that uses a backslash based introducer in place of it (backslash backslash, forward slash backslash, or backslash forward slash) is…

more

parsed with no authority and folds into the path. Node's native WHATWG URL parser instead treats a backslash as interchangeable with a forward slash for special schemes, so the two parsers extract different hosts from the same input. Applications that use fast-uri to enforce host based policy such as allowlists, SSRF filtering, or redirect validation before passing the same URL into Node's URL or fetch consumers can be steered to an unintended host. Upgrade to fast-uri 4.1.2, 3.1.5, or 2.4.4.

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-75931Same product: Openjsf Fast-Uri
CVE-2026-84394Same product: Openjsf Fast-Uri
CVE-2026-16221Same product: Openjsf Fast-Uri
CVE-2026-13676Same product: Openjsf Fast-Uri
CVE-2026-6322Same product: Openjsf Fast-Uri
CVE-2026-75899Same product: Openjsf Fast-Uri
CVE-2026-76172Same product: Openjsf Fast-Uri
CVE-2026-75975Same product: Openjsf Fast-Uri
CVE-2026-84292Same product: Openjsf Fast-Uri
CVE-2026-6321Same product: Openjsf Fast-Uri

Affected Assets

openjsf
fast-uri
≤ 2.4.4 · 3.0.0 — 3.1.5 · 4.0.0 — 4.1.2

Mitigating Controls

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Developer testing and evaluation can discover cases where two products interpret the same inputs or state transitions differently.

Strict, consistently applied input validation reduces the chance that one product will accept data the other product rejects or interprets differently.

Applying security engineering principles during design can require unambiguous protocol and data-format specifications that eliminate divergent interpretations between products.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Security testing can detect and correct cases where one component misinterprets another’s state or messages.

prevents

Secure coding standards can enforce canonical input handling and strict protocol compliance to avoid misinterpretation between products.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-436, a class-level weakness, and none of its children carries one either.

References