CVE-2026-18427

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.7% (49th percentile of EPSS-scored CVEs). 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
7.5EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.5Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

@fastify/static before version 10.1.3 contains an incomplete fix for a previous route guard bypass. The static file handler rejected only parent directory segments, but it did not canonicalize dot segments, duplicate slashes, encoded dots, or backslashes before route matching and before delegating to the send layer. As a result, an unauthenticated attacker could request a file protected by a route based guard using a non canonical path form that misses the guarded route yet resolves back onto the protected file, disclosing its contents. Applications that protect a subtree of the static root with a route based guard are affected, while applications relying on the allowedPath option are not. This is fixed in @fastify/static 10.1.3, which canonicalizes the pathname, including rejecting backslashes, on the path used for routing and serving.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
39
EG Risk 39/100CISA SSVC

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%
Exploitation1% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.7%
EPSS %ILE
50th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 6, 2026

Last Modified

September 4, 2026

Advisory Details (2)

Auto-updated Aug 6, 2026
No fix on record yet. Sources: github.
githubMentions a patch (unverified)

@fastify/static vulnerable to route guard bypass via non-canonical path segments · Advisory · fastify/fastify-static · GitHub

https://github.com/fastify/fastify-static/security/advisories/GHSA-423g-23ch-w7c6
generic

Security Advisories | OpenJS Foundation CVE Numbering Authority

https://cna.openjsf.org/security-advisories.html

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 44× 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 106 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-18427?
CVE-2026-18427 is a high vulnerability published on August 6, 2026. @fastify/static before version 10.1.3 contains an incomplete fix for a previous route guard bypass. The static file handler rejected only parent directory segments, but it did not canonicalize dot segments, duplicate slashes, encoded dots, or backslashes before route matching and before delegating…
When was CVE-2026-18427 disclosed?
CVE-2026-18427 was first published on August 6, 2026, with the most recent update on September 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18427 actively exploited?
CVE-2026-18427 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-18427?
CVE-2026-18427 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-18427?
No fix for CVE-2026-18427 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-18427

Explore →

Is Your Infrastructure Affected by CVE-2026-18427?

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

Book a Demo →Browse All CVEs