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

September 2, 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(4)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatopenshift4/ose-monitoring-plugin-rhel9:17882357122026-09-10redhat
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.4-1 (13 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 22× in last 7d / 98× 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.

Showing the most recent 100 of 169 total refreshes for this CVE.

  1. 2026-09-19 01:19 UTCEG score recompute
  2. 2026-09-19 01:19 UTCVendor advisory
  3. 2026-09-18 19:27 UTCEPSS rescore
  4. 2026-09-18 13:31 UTCVendor advisory
  5. 2026-09-18 01:16 UTCEG score recompute
  6. 2026-09-18 01:16 UTCVendor advisory
  7. 2026-09-17 01:24 UTCEG score recompute
  8. 2026-09-17 01:24 UTCVendor advisory
  9. 2026-09-16 14:07 UTCEPSS rescore
  10. 2026-09-16 05:29 UTCEG score recompute
  11. 2026-09-16 05:29 UTCVendor advisory
  12. 2026-09-16 05:14 UTCEPSS rescore
  13. 2026-09-15 03:02 UTCVendor advisory
  14. 2026-09-14 11:54 UTCVendor advisory
  15. 2026-09-14 00:24 UTCEG score recompute
  16. 2026-09-14 00:24 UTCVendor advisory
  17. 2026-09-13 16:46 UTCEPSS rescore
  18. 2026-09-13 12:55 UTCVendor advisory
  19. 2026-09-13 01:26 UTCEG score recompute
  20. 2026-09-13 01:26 UTCVendor advisory
  21. 2026-09-12 15:00 UTCEPSS rescore
  22. 2026-09-12 13:57 UTCVendor advisory
  23. 2026-09-12 02:28 UTCVendor advisory
  24. 2026-09-11 14:58 UTCEG score recompute
  25. 2026-09-11 14:58 UTCVendor advisory
Show 75 more
  1. 2026-09-11 14:52 UTCEPSS rescore
  2. 2026-09-11 09:36 UTCEPSS rescore
  3. 2026-09-11 02:23 UTCVendor advisory
  4. 2026-09-10 14:52 UTCEG score recompute
  5. 2026-09-10 14:52 UTCVendor advisory
  6. 2026-09-10 09:34 UTCEPSS rescore
  7. 2026-09-10 03:22 UTCVendor advisory
  8. 2026-09-09 07:05 UTCEG score recompute
  9. 2026-09-09 07:05 UTCVendor advisory
  10. 2026-09-08 22:00 UTCEPSS rescore
  11. 2026-09-07 19:34 UTCEG score recompute
  12. 2026-09-07 19:34 UTCVendor advisory
  13. 2026-09-07 16:01 UTCEPSS rescore
  14. 2026-09-06 18:15 UTCEG score recompute
  15. 2026-09-06 18:15 UTCVendor advisory
  16. 2026-09-06 13:47 UTCEPSS rescore
  17. 2026-09-06 06:36 UTCVendor advisory
  18. 2026-09-05 18:46 UTCEG score recompute
  19. 2026-09-05 18:46 UTCVendor advisory
  20. 2026-09-05 04:45 UTCEG score recompute
  21. 2026-09-05 04:45 UTCVendor advisory
  22. 2026-09-04 10:30 UTCEG score recompute
  23. 2026-09-04 10:30 UTCVendor advisory
  24. 2026-09-04 05:06 UTCEPSS rescore
  25. 2026-09-03 21:10 UTCVendor advisory
  26. 2026-09-03 09:10 UTCVendor advisory
  27. 2026-09-02 14:46 UTCEG score recompute
  28. 2026-09-02 14:46 UTCVendor advisory
  29. 2026-09-02 14:11 UTCEPSS rescore
  30. 2026-09-01 22:34 UTCEG score recompute
  31. 2026-09-01 22:33 UTCVendor advisory
  32. 2026-09-01 13:53 UTCEPSS rescore
  33. 2026-09-01 04:39 UTCEPSS rescore
  34. 2026-08-31 23:25 UTCVendor advisory
  35. 2026-08-30 21:39 UTCEG score recompute
  36. 2026-08-30 21:39 UTCVendor advisory
  37. 2026-08-30 19:17 UTCEPSS rescore
  38. 2026-08-30 10:10 UTCEG score recompute
  39. 2026-08-30 10:10 UTCVendor advisory
  40. 2026-08-30 01:22 UTCEPSS rescore
  41. 2026-08-29 22:23 UTCEG score recompute
  42. 2026-08-29 22:23 UTCVendor advisory
  43. 2026-08-28 21:41 UTCEPSS rescore
  44. 2026-08-28 21:09 UTCVendor advisory
  45. 2026-08-27 20:46 UTCEG score recompute
  46. 2026-08-27 20:46 UTCVendor advisory
  47. 2026-08-27 14:25 UTCEPSS rescore
  48. 2026-08-27 08:50 UTCVendor advisory
  49. 2026-08-26 19:15 UTCEG score recompute
  50. 2026-08-26 19:15 UTCVendor advisory
  51. 2026-08-26 14:46 UTCEPSS rescore
  52. 2026-08-26 05:03 UTCVendor advisory
  53. 2026-08-25 17:32 UTCEG score recompute
  54. 2026-08-25 17:32 UTCVendor advisory
  55. 2026-08-25 13:48 UTCEPSS rescore
  56. 2026-08-25 05:40 UTCVendor advisory
  57. 2026-08-24 18:12 UTCEG score recompute
  58. 2026-08-24 18:12 UTCVendor advisory
  59. 2026-08-24 06:42 UTCVendor advisory
  60. 2026-08-23 19:13 UTCVendor advisory
  61. 2026-08-23 07:44 UTCEG score recompute
  62. 2026-08-23 07:44 UTCVendor advisory
  63. 2026-08-23 00:19 UTCEPSS rescore
  64. 2026-08-22 20:15 UTCVendor advisory
  65. 2026-08-22 08:46 UTCEG score recompute
  66. 2026-08-22 08:46 UTCVendor advisory
  67. 2026-08-21 23:49 UTCEPSS rescore
  68. 2026-08-21 21:17 UTCVendor advisory
  69. 2026-08-21 09:48 UTCEG score recompute
  70. 2026-08-21 09:48 UTCVendor advisory
  71. 2026-08-20 22:55 UTCEPSS rescore
  72. 2026-08-20 22:19 UTCVendor advisory
  73. 2026-08-20 10:49 UTCVendor advisory
  74. 2026-08-19 23:19 UTCEG score recompute
  75. 2026-08-19 23:19 UTCVendor advisory

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, with the most recent update on September 2, 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.0% 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