CVE-2026-15144: @fastify/rate-limit vulnerable to rate-limit bypass via IPv6 address rotation
@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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
@fastify/rate-limitto a version that resolves this vulnerability.Fixed in 11.2.0
Event History
Frequently Asked Questions
What is the severity of CVE-2026-15144?
The severity of CVE-2026-15144 is high with a CVSS score of 7.3.
What is the risk associated with CVE-2026-15144?
CVE-2026-15144 has a risk rating of 51, indicating a significant risk level.
How do I fix CVE-2026-15144?
Upgrade @fastify/rate-limit to version 11.2.0 or higher to mitigate the vulnerability in CVE-2026-15144.
What does CVE-2026-15144 affect?
CVE-2026-15144 affects the @fastify/rate-limit package prior to version 11.2.0.
What type of attack does CVE-2026-15144 allow?
CVE-2026-15144 allows rate-limit bypass via IPv6 address rotation.