{"schemaVersion":1,"url":"https://cve.openhack.com/cve/CVE-2026-15144","id":"CVE-2026-15144","title":"@fastify/rate-limit vulnerable to rate-limit bypass via IPv6 address rotation","description":"@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 d","descriptionLong":"@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.","published":"2026-07-29T16:10:24.560Z","updated":"2026-10-28T02:30:32.559770223Z","reserved":"2026-07-08T17:27:38.479Z","status":"Analyzed","rejected":false,"assigner":"openjs","metric":{"version":"3.1","score":7.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","rating":"high","source":"openjs"},"metrics":[{"version":"3.1","score":7.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","rating":"high","source":"openjs"},{"version":"3.1","score":7.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","rating":"high","source":"ce714d77-add3-4f53-aff5-83d477b104bb"},{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","rating":"medium","source":"NVD"},{"version":"3.1","score":7.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","rating":"high","source":"OSV"}],"rating":"high","products":["@fastify/rate-limit"],"affectedProducts":[{"vendor":"@fastify/rate-limit","product":"@fastify/rate-limit","defaultStatus":"unaffected","versions":[{"versionType":"semver","status":"affected","version":"0","lessThan":"11.2.0"},{"versionType":"semver","status":"unaffected","version":"11.2.0"}],"platforms":[]}],"packages":[],"cwes":["CWE-307","CWE-770"],"aliases":["GHSA-grpc-p53c-r64v"],"references":[{"url":"https://github.com/fastify/fastify-rate-limit/security/advisories/GHSA-grpc-p53c-r64v","tags":["Vendor Advisory","advisory"]},{"url":"https://cna.openjsf.org/security-advisories.html","tags":["Vendor Advisory","advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/15xxx/CVE-2026-15144.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-15144","tags":["advisory"]}],"patchReferenced":false,"fixAvailable":false,"exploitReferenced":false,"kev":false,"kevAdded":null,"kevDue":null,"kevEntry":null,"ssvc":{"exploitation":"none","automatable":"yes","technicalImpact":"partial"},"epss":0.00395,"epssPercentile":0.34585,"sources":[{"name":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2026-15144","ok":true},{"name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-15144","ok":true,"note":"Analyzed"},{"name":"OSV","url":"https://osv.dev/vulnerability/CVE-2026-15144","ok":true,"note":"0 packages"},{"name":"CISA KEV","url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","ok":true,"note":"not listed"},{"name":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-15144","ok":true,"note":"scored 2026-11-20"}],"aiTitle":false,"tech":[],"critical":[],"attention":null}