GHSA-46WH-PXPV-Q5GQ
Vulnerability from github – Published: 2026-03-06 18:36 – Updated: 2026-03-09 15:58Summary
The default keyGenerator in express-rate-limit applies IPv6 subnet masking (/56 by default) to all addresses that net.isIPv6() returns true for. This includes IPv4-mapped IPv6 addresses (::ffff:x.x.x.x), which Node.js returns as request.ip on dual-stack servers.
Because the first 80 bits of all IPv4-mapped addresses are zero, a /56 (or any /32 to /80) subnet mask produces the same network key (::/56) for every IPv4 client. This collapses all IPv4 traffic into a single rate-limit bucket: one client exhausting the limit causes HTTP 429 for all other IPv4 clients.
Details
Root Cause
In source/ip-key-generator.ts:
export function ipKeyGenerator(ip: string, ipv6Subnet: number | false = 56) {
if (ipv6Subnet && isIPv6(ip)) {
return `${new Address6(`${ip}/${ipv6Subnet}`).startAddress().correctForm()}/${ipv6Subnet}`
}
return ip
}
net.isIPv6('::ffff:192.168.1.1') returns true, so IPv4-mapped addresses enter the subnet masking path. With a /56 prefix, the start address for any ::ffff:x.x.x.x is ::, producing the key ::/56.
Proof of Concept
const { isIPv6 } = require('net');
const { Address6 } = require('ip-address');
function ipKeyGenerator(ip, ipv6Subnet = 56) {
if (ipv6Subnet && isIPv6(ip)) {
return `${new Address6(`${ip}/${ipv6Subnet}`).startAddress().correctForm()}/${ipv6Subnet}`;
}
return ip;
}
console.log(ipKeyGenerator('::ffff:192.168.1.1', 56)); // ::/56
console.log(ipKeyGenerator('::ffff:10.0.0.1', 56)); // ::/56
console.log(ipKeyGenerator('::ffff:8.8.8.8', 56)); // ::/56
// ALL produce '::/56' — same bucket
End-to-End Validation
On a dual-stack Express server (app.listen(port, '::')), tested with Express 5.2.1:
- request.ip for IPv4 clients is ::ffff:127.0.0.1
- Rate limit key resolves to ::/56
- After limit requests from any IPv4 client, all other IPv4 clients receive 429
When This Occurs
- Node.js dual-stack servers (default on Linux when listening on
::) - Any environment where
request.ipcontains IPv4-mapped IPv6 addresses - Only affects the default
keyGenerator(custom key generators are not affected)
Impact
- Denial of Service: A single client can block all IPv4 traffic by exhausting the shared rate limit
- Affects default configuration: No special options needed to trigger this
Affected Versions
All versions of express-rate-limit between v8.0.0 and v8.2.1.
Fix
This issue was fixed in commit 14e53888cdfd1b9798faf5b634c4206409e27fc4. This fix has been included in release v8.3.0, and backported to all affected minor versions in the form of releases v8.2.2, v8.1.1, and v8.0.2.
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "express-rate-limit"
},
"ranges": [
{
"events": [
{
"introduced": "8.2.0"
},
{
"fixed": "8.2.2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "npm",
"name": "express-rate-limit"
},
"ranges": [
{
"events": [
{
"introduced": "8.1.0"
},
{
"fixed": "8.1.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"8.1.0"
]
},
{
"package": {
"ecosystem": "npm",
"name": "express-rate-limit"
},
"ranges": [
{
"events": [
{
"introduced": "8.0.0"
},
{
"fixed": "8.0.2"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-30827"
],
"database_specific": {
"cwe_ids": [
"CWE-770"
],
"github_reviewed": true,
"github_reviewed_at": "2026-03-06T18:36:56Z",
"nvd_published_at": "2026-03-07T06:16:10Z",
"severity": "HIGH"
},
"details": "## Summary\n\nThe default `keyGenerator` in express-rate-limit applies IPv6 subnet masking (`/56` by default) to all addresses that `net.isIPv6()` returns true for. This includes IPv4-mapped IPv6 addresses (`::ffff:x.x.x.x`), which Node.js returns as `request.ip` on dual-stack servers.\n\nBecause the first 80 bits of all IPv4-mapped addresses are zero, a `/56` (or any `/32` to `/80`) subnet mask produces the same network key (`::/56`) for **every** IPv4 client. This collapses all IPv4 traffic into a single rate-limit bucket: one client exhausting the limit causes HTTP 429 for all other IPv4 clients.\n\n## Details\n\n### Root Cause\n\nIn `source/ip-key-generator.ts`:\n\n```typescript\nexport function ipKeyGenerator(ip: string, ipv6Subnet: number | false = 56) {\n if (ipv6Subnet \u0026\u0026 isIPv6(ip)) {\n return `${new Address6(`${ip}/${ipv6Subnet}`).startAddress().correctForm()}/${ipv6Subnet}`\n }\n return ip\n}\n```\n\n`net.isIPv6(\u0027::ffff:192.168.1.1\u0027)` returns `true`, so IPv4-mapped addresses enter the subnet masking path. With a `/56` prefix, the start address for any `::ffff:x.x.x.x` is `::`, producing the key `::/56`.\n\n### Proof of Concept\n\n```javascript\nconst { isIPv6 } = require(\u0027net\u0027);\nconst { Address6 } = require(\u0027ip-address\u0027);\n\nfunction ipKeyGenerator(ip, ipv6Subnet = 56) {\n if (ipv6Subnet \u0026\u0026 isIPv6(ip)) {\n return `${new Address6(`${ip}/${ipv6Subnet}`).startAddress().correctForm()}/${ipv6Subnet}`;\n }\n return ip;\n}\n\nconsole.log(ipKeyGenerator(\u0027::ffff:192.168.1.1\u0027, 56)); // ::/56\nconsole.log(ipKeyGenerator(\u0027::ffff:10.0.0.1\u0027, 56)); // ::/56\nconsole.log(ipKeyGenerator(\u0027::ffff:8.8.8.8\u0027, 56)); // ::/56\n// ALL produce \u0027::/56\u0027 \u2014 same bucket\n```\n\n### End-to-End Validation\n\nOn a dual-stack Express server (`app.listen(port, \u0027::\u0027)`), tested with Express 5.2.1:\n- `request.ip` for IPv4 clients is `::ffff:127.0.0.1`\n- Rate limit key resolves to `::/56`\n- After `limit` requests from any IPv4 client, all other IPv4 clients receive 429\n\n### When This Occurs\n\n- Node.js dual-stack servers (default on Linux when listening on `::`)\n- Any environment where `request.ip` contains IPv4-mapped IPv6 addresses\n- Only affects the default `keyGenerator` (custom key generators are not affected)\n\n## Impact\n\n- **Denial of Service**: A single client can block all IPv4 traffic by exhausting the shared rate limit\n- **Affects default configuration**: No special options needed to trigger this\n\n## Affected Versions\n\nAll versions of express-rate-limit between v8.0.0 and v8.2.1.\n\n## Fix\n\nThis issue was fixed in commit 14e53888cdfd1b9798faf5b634c4206409e27fc4. This fix has been included in release v8.3.0, and backported to all affected minor versions in the form of releases v8.2.2, v8.1.1, and v8.0.2.",
"id": "GHSA-46wh-pxpv-q5gq",
"modified": "2026-03-09T15:58:09Z",
"published": "2026-03-06T18:36:56Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/express-rate-limit/express-rate-limit/security/advisories/GHSA-46wh-pxpv-q5gq"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-30827"
},
{
"type": "WEB",
"url": "https://github.com/express-rate-limit/express-rate-limit/commit/14e53888cdfd1b9798faf5b634c4206409e27fc4"
},
{
"type": "PACKAGE",
"url": "https://github.com/express-rate-limit/express-rate-limit"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "express-rate-limit: IPv4-mapped IPv6 addresses bypass per-client rate limiting on servers with dual-stack network"
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.