CVE-2026-18446

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 87% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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 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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
13%
KEV
Not listed

Published

July 31, 2026

Last Modified

July 31, 2026

Advisory Details (2)

Auto-updated Jul 31, 2026
Patch available. Sources: github.
generic

Security Advisories | OpenJS Foundation CVE Numbering Authority

https://cna.openjsf.org/security-advisories.html
github Patch Available

fast-uri vulnerable to host confusion via backslash authority introducer · Advisory · fastify/fast-uri · GitHub

https://github.com/fastify/fast-uri/security/advisories/GHSA-7p8r-x3mc-p8w7

Vendor Advisories for CVE-2026-18446(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatgrafana13-1-main-13.1.1-0.4.hum12026-08-01redhat
redhatgrafana12-4-main-12.4.6-0.3.hum12026-08-01redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-ajv8.12.0~ds+~2.1.1-5 ... 8.20.0~ds+~cs7.1.3-1 (10 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-ajv8.12.0~ds+~2.1.1-5 ... 8.20.0~ds+~cs7.1.2-1 (9 versions)8.20.0~ds+~cs7.1.3-1—
npm(1)
PackageVulnerable rangeFixed inDependents
fast-uri—4.1.2—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 28× in last 7d / 52× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-15 15:22 UTCVendor advisory
  2. 2026-08-15 03:53 UTCEG score recompute
  3. 2026-08-15 03:53 UTCVendor advisory
  4. 2026-08-15 01:30 UTCEPSS rescore
  5. 2026-08-14 16:23 UTCVendor advisory
  6. 2026-08-14 04:54 UTCEG score recompute
  7. 2026-08-14 04:54 UTCVendor advisory
  8. 2026-08-13 22:00 UTCEPSS rescore
  9. 2026-08-13 17:25 UTCVendor advisory
  10. 2026-08-13 05:57 UTCVendor advisory
  11. 2026-08-12 18:28 UTCEG score recompute
  12. 2026-08-12 18:28 UTCVendor advisory
  13. 2026-08-12 13:50 UTCEPSS rescore
  14. 2026-08-12 06:59 UTCVendor advisory
  15. 2026-08-11 19:30 UTCEG score recompute
  16. 2026-08-11 19:30 UTCVendor advisory
  17. 2026-08-11 13:42 UTCEPSS rescore
  18. 2026-08-11 08:01 UTCEG score recompute
  19. 2026-08-11 08:01 UTCVendor advisory
  20. 2026-08-11 00:00 UTCEPSS rescore
  21. 2026-08-10 20:32 UTCVendor advisory
  22. 2026-08-10 09:02 UTCVendor advisory
  23. 2026-08-09 21:32 UTCEG score recompute
  24. 2026-08-09 21:32 UTCVendor advisory
  25. 2026-08-09 13:46 UTCEPSS rescore
Show 27 more
  1. 2026-08-09 10:03 UTCVendor advisory
  2. 2026-08-08 22:34 UTCEG score recompute
  3. 2026-08-08 22:34 UTCVendor advisory
  4. 2026-08-08 16:37 UTCEPSS rescore
  5. 2026-08-08 11:05 UTCVendor advisory
  6. 2026-08-07 23:36 UTCEG score recompute
  7. 2026-08-07 23:36 UTCVendor advisory
  8. 2026-08-07 12:07 UTCVendor advisory
  9. 2026-08-07 00:38 UTCEG score recompute
  10. 2026-08-07 00:38 UTCVendor advisory
  11. 2026-08-06 13:46 UTCEPSS rescore
  12. 2026-08-06 13:10 UTCVendor advisory
  13. 2026-08-06 01:40 UTCEG score recompute
  14. 2026-08-06 01:40 UTCVendor advisory
  15. 2026-08-05 19:17 UTCEPSS rescore
  16. 2026-08-05 14:12 UTCVendor advisory
  17. 2026-08-05 01:45 UTCEG score recompute
  18. 2026-08-04 15:10 UTCEPSS rescore
  19. 2026-08-04 14:16 UTCEG score recompute
  20. 2026-08-04 10:38 UTCEPSS rescore
  21. 2026-08-02 04:47 UTCEG score recompute
  22. 2026-08-02 02:26 UTCEPSS rescore
  23. 2026-07-31 18:19 UTCEG score recompute
  24. 2026-07-31 18:04 UTCEG score recompute
  25. 2026-07-31 15:27 UTCEG score recompute
  26. 2026-07-31 14:50 UTCEG score recompute
  27. 2026-07-31 14:48 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-18446?
CVE-2026-18446 is a high vulnerability published on July 31, 2026. 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 parsed with no authority and folds into…
When was CVE-2026-18446 disclosed?
CVE-2026-18446 was first published in the National Vulnerability Database on July 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18446 actively exploited?
CVE-2026-18446 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 87.2% of all scored CVEs.
What is the CVSS score of CVE-2026-18446?
CVE-2026-18446 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-18446?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18446, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-18446

Explore →

Is Your Infrastructure Affected by CVE-2026-18446?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs