CVE-2026-15144

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.4% (31st 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, nvd
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.3Exploit: 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/rate-limit before 11.2.0 keys rate-limit buckets by the verbatim client IP string returned from request.ip. Because a single IPv6 client can control a large address range (a /64 holds 2^64 distinct addresses) and the same address has multiple valid textual representations, an IPv6 capable client can defeat the rate-limit boundary by rotating addresses or by rewriting the same address in different forms. Applications that use @fastify/rate-limit to protect endpoints such as authentication, password reset, OTP delivery, or expensive API calls can be bypassed by IPv6 clients behind a proxy that surfaces IPv6 to the origin when trustProxy is enabled. The issue is fixed in @fastify/rate-limit 11.2.0, where the default key generator normalizes IPv6 addresses to their canonical form, collapses IPv4 mapped IPv6 to IPv4, and applies a configurable prefix mask (default /64) via a new ipv6Subnet option.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
29
EG Risk 29/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
Severity53% × 45%
Exploitation0% × 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.4%
EPSS %ILE
31st
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

July 29, 2026

Last Modified

August 5, 2026

Advisory Details (2)

Auto-updated Jul 29, 2026
No fix on record yet. Sources: github.
generic

Security Advisories | OpenJS Foundation CVE Numbering Authority

https://cna.openjsf.org/security-advisories.html
githubMentions a patch (unverified)

@fastify/rate-limit vulnerable to rate-limit bypass via IPv6 address rotation · Advisory · fastify/fastify-rate-limit · GitHub

https://github.com/fastify/fastify-rate-limit/security/advisories/GHSA-grpc-p53c-r64v

Weakness Classification(2)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-15144?
CVE-2026-15144 is a medium vulnerability published on July 29, 2026. @fastify/rate-limit before 11.2.0 keys rate-limit buckets by the verbatim client IP string returned from request.ip. Because a single IPv6 client can control a large address range (a /64 holds 2^64 distinct addresses) and the same address has multiple valid textual representations, an IPv6 capable…
When was CVE-2026-15144 disclosed?
CVE-2026-15144 was first published on July 29, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15144 actively exploited?
CVE-2026-15144 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-15144?
CVE-2026-15144 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-15144?
No fix for CVE-2026-15144 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-15144

Explore →

Is Your Infrastructure Affected by CVE-2026-15144?

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

Book a Demo →Browse All CVEs