{"id":"CVE-2026-65624","aliases":["AZL-94308","DEBIAN-CVE-2026-65624","EEF-CVE-2026-65624","EUVD-2026-49740","GHSA-v9x8-262p-f2g5","RHSA-2026:47231","RHSA-2026:47236","RHSA-2026:57882","UBUNTU-CVE-2026-65624"],"status":"published","title":"Cowboy HTTP/1.1 max_headers Bypass via Duplicate Header Names Enables Memory Exhaustion","description":"Allocation of Resources Without Limits or Throttling vulnerability in ninenines cowboy allows an unauthenticated remote attacker to exhaust connection process memory over HTTP/1.1.\n\nThe HTTP/1.1 handler in cowboy_http enforces the max_headers limit by counting the number of distinct header names in a map (maps:size(Headers)). When a request contains multiple header lines with the same name, the values are concatenated into a single ever-growing binary stored under that one map key (\", \" for regular headers, \"; \" for cookies), so the map size stays at one and the max_headers cap (default 100) is never reached. Because no accumulator bounds the total number of header lines or the total byte size of the header block (only per-line max_header_name_length and max_header_value_length apply), an unauthenticated client can send an arbitrary number of header lines with the same name and grow the connection process's binary memory to arbitrary size within the request window.\n\nThe impact per connection is bounded by request_timeout (default 5 seconds, not reset by header data), and by max_heap_size when set (the offending connection process is killed once its heap grows past the limit). When max_heap_size is left at the default (unset), sustained abuse can drive the Erlang VM into out-of-memory conditions.\n\nThis issue affects cowboy from 2.0.0-pre.4 before 2.18.0.","severity":{"version":"4.0","score":6.9,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-09","score":0.00383,"percentile":0.32688,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-770"],"published":"2026-07-28T10:01:01Z","modified":"2026-11-05T05:40:51Z","fixes":[{"ecosystem":"Azure Linux:3","package":"rabbitmq-server","fixed_in":["3.13.7-9"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"erlang-cowboy","fixed_in":["2.18.0+dfsg-1"],"sources":["osv"]},{"ecosystem":"Hex","package":"cowboy","fixed_in":["2.18.0"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Azure Linux:3","package":"rabbitmq-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.13.7-9"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"erlang-cowboy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.18.0+dfsg-1"}]}],"versions":["0.10.0+dfsg1-1","0.6.1-1","0.6.1-2","0.6.1-3","0.6.1-4","0.8.6+dfsg-1","0.8.6+dfsg1-1","1.0.0+dfsg1-1","2.0.0~pre.1+dfsg1-1","2.0.0~pre.1+dfsg1-2","2.0.0~pre.1+dfsg1-3","2.0.0~pre.1+dfsg1-4","2.16.1+dfsg-1","2.16.1+dfsg-2","2.17.0+dfsg-1"]},{"source":"osv","ecosystem":"Hex","package":"cowboy","ranges":[{"type":"SEMVER","events":[{"introduced":"2.0.0-pre.4"},{"fixed":"2.18.0"}]}],"versions":["2.0.0","2.1.0","2.10.0","2.11.0","2.12.0","2.13.0","2.14.0","2.14.1","2.14.2","2.15.0","2.16.0","2.16.1","2.17.0","2.2.0","2.2.1","2.2.2","2.3.0","2.4.0","2.5.0","2.6.0","2.6.1","2.6.2","2.6.3","2.7.0","2.8.0","2.9.0"]},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"rabbitmq-server4.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.3.4-0.2.hum1"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"rabbitmq-server4.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.2.9-0.2.hum1"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"rabbitmq-server4.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.3.5-0.1.hum1"}]}],"bundled":2},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"rabbitmq-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.5.4-1","3.5.4-3","3.5.4-3.1","3.5.7-1","3.5.7-1ubuntu0.16.04.1","3.5.7-1ubuntu0.16.04.2","3.5.7-1ubuntu0.16.04.4","3.5.7-1ubuntu0.16.04.4+esm1","3.5.7-1ubuntu0.16.04.4+esm2","3.5.7-1ubuntu0.16.04.4+esm3"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"erlang-cowboy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.0.0~pre.1+dfsg1-1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"rabbitmq-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.6.10-1","3.6.10-1ubuntu0.1","3.6.10-1ubuntu0.3","3.6.10-1ubuntu0.4","3.6.10-1ubuntu0.5","3.6.10-1ubuntu0.5+esm1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"erlang-cowboy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.0.0~pre.1+dfsg1-2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"rabbitmq-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.7.8-4ubuntu2","3.7.18-1","3.8.2-0ubuntu1","3.8.2-0ubuntu1.1","3.8.2-0ubuntu1.2","3.8.2-0ubuntu1.3","3.8.2-0ubuntu1.4","3.8.2-0ubuntu1.5","3.8.3-0ubuntu0.1","3.8.3-0ubuntu0.2","3.8.3-0ubuntu0.3","3.8.3-0ubuntu0.3+esm1","3.8.3-0ubuntu0.3+esm2"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"erlang-cowboy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.0.0~pre.1+dfsg1-4"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"erlang-cowboy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.0.0~pre.1+dfsg1-4"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"rabbitmq-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.8.9-3ubuntu1","3.9.8-1","3.9.8-2","3.9.8-3","3.9.8-5","3.9.8-6","3.9.13-1","3.9.13-1ubuntu0.22.04.1","3.9.13-1ubuntu0.22.04.2","3.9.27-0ubuntu0.1","3.9.27-0ubuntu0.2","3.9.27-0ubuntu0.5","3.9.27-0ubuntu0.6"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"erlang-cowboy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.0.0~pre.1+dfsg1-4"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"rabbitmq-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.12.1-1","3.12.1-1ubuntu1","3.12.1-1ubuntu1.2","3.12.1-1ubuntu1.4","3.12.1-1ubuntu1.6","3.12.1-1ubuntu1.7"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"erlang-cowboy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.0.0~pre.1+dfsg1-4build1","2.18.0+dfsg-1"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"rabbitmq-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.0.5-10ubuntu5","4.3.2-4ubuntu2","4.3.2-4ubuntu3"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"erlang-cowboy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.0.0~pre.1+dfsg1-4","2.0.0~pre.1+dfsg1-4build1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"rabbitmq-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.0.5-8ubuntu2","4.0.5-10ubuntu1","4.0.5-10ubuntu2","4.0.5-10ubuntu3","4.0.5-10ubuntu4","4.0.5-10ubuntu5","4.0.5-10ubuntu5.1","4.0.5-10ubuntu5.2"]}],"products":[{"vendor":"ninenines","product":"cowboy"}],"references":[{"url":"https://cna.erlef.org/cves/CVE-2026-65624.html","tags":["related","third-party-advisory","advisory","web","article","report"]},{"url":"https://osv.dev/vulnerability/EEF-CVE-2026-65624","tags":["related","web","article","report"]},{"url":"https://github.com/ninenines/cowboy/commit/3a34d8c1cfd94326466aa16a9017236691dc9c55","tags":["patch","fix","article"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-65624","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-v9x8-262p-f2g5"},{"url":"https://github.com","tags":["web"]},{"url":"https://repo.hex.pm","tags":["web"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/65xxx/CVE-2026-65624.json","tags":["advisory"]},{"url":"https://github.com/ninenines/cowboy","tags":["package"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2026-65624","tags":["advisory"]},{"url":"https://hex.pm/packages/cowboy","tags":["package"]},{"url":"https://access.redhat.com/errata/RHSA-2026:47231","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-59248","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-65624","tags":["report"]},{"url":"https://access.redhat.com/security/updates/classification/","tags":["article"]},{"url":"https://images.redhat.com/","tags":["article"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_47231.json","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2507959","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-59248","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-59248","tags":["advisory"]},{"url":"https://cna.erlef.org/cves/CVE-2026-59248.html","tags":["article"]},{"url":"https://github.com/ninenines/cowlib/commit/f582430498072a0c65ad338030321576dc13a343","tags":["article"]},{"url":"https://osv.dev/vulnerability/EEF-CVE-2026-59248","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2507960","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-65624","tags":["advisory","report"]},{"url":"https://access.redhat.com/errata/RHSA-2026:47236","tags":["advisory"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_47236.json","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2026:57882","tags":["advisory"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_57882.json","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2026-65624","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2026-65624","title":"Cowboy HTTP/1.1 max_headers Bypass via Duplicate Header Names Enables Memory Exhaustion","description":"Allocation of Resources Without Limits or Throttling vulnerability in ninenines cowboy allows an unauthenticated remote attacker to exhaust connection process memory over HTTP/1.1.\n\nThe HTTP/1.1 handler in cowboy_http enforces the max_headers limit by counting the number of distinct header names in a map (maps:size(Headers)). When a request contains multiple header lines with the same name, the values are concatenated into a single ever-growing binary stored under that one map key (\", \" for regular headers, \"; \" for cookies), so the map size stays at one and the max_headers cap (default 100) is never reached. Because no accumulator bounds the total number of header lines or the total byte size of the header block (only per-line max_header_name_length and max_header_value_length apply), an unauthenticated client can send an arbitrary number of header lines with the same name and grow the connection process's binary memory to arbitrary size within the request window.\n\nThe impact per connection is bounded by request_timeout (default 5 seconds, not reset by header data), and by max_heap_size when set (the offending connection process is killed once its heap grows past the limit). When max_heap_size is left at the default (unset), sustained abuse can drive the Erlang VM into out-of-memory conditions.\n\nThis issue affects cowboy from 2.0.0-pre.4 before 2.18.0.","status":"published","published":"2026-07-28T10:01:01.811Z","modified":"2026-07-29T04:17:22.788Z","cvss":[{"version":"4.0","score":6.9,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","level":"medium","assessor":"cna"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T13:37:02.780526Z"}],"euvd":[{"id":"EUVD-2026-49740","description":"Allocation of Resources Without Limits or Throttling vulnerability in ninenines cowboy allows an unauthenticated remote attacker to exhaust connection process memory over HTTP/1.1.\n\nThe HTTP/1.1 handler in cowboy_http enforces the max_headers limit by counting the number of distinct header names in a map (maps:size(Headers)). When a request contains multiple header lines with the same name, the values are concatenated into a single ever-growing binary stored under that one map key (\", \" for regular headers, \"; \" for cookies), so the map size stays at one and the max_headers cap (default 100) is never reached. Because no accumulator bounds the total number of header lines or the total byte size of the header block (only per-line max_header_name_length and max_header_value_length apply), an unauthenticated client can send an arbitrary number of header lines with the same name and grow the connection process's binary memory to arbitrary size within the request window.\n\nThe impact per connection is bounded by request_timeout (default 5 seconds, not reset by header data), and by max_heap_size when set (the offending connection process is killed once its heap grows past the limit). When max_heap_size is left at the default (unset), sustained abuse can drive the Erlang VM into out-of-memory conditions.\n\nThis issue affects cowboy from 2.0.0-pre.4 before 2.18.0.","status":"published","published":"2026-07-28T10:01:01Z","modified":"2026-07-29T04:17:22Z","cvss":[{"version":"4.0","score":6.9,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","level":"medium"}],"updated_at":"2026-11-02T18:02:30.59681Z"}],"ghsa":[{"id":"GHSA-v9x8-262p-f2g5","title":"Allocation of Resources Without Limits or Throttling vulnerability in ninenines cowboy allows an...","description":"Allocation of Resources Without Limits or Throttling vulnerability in ninenines cowboy allows an unauthenticated remote attacker to exhaust connection process memory over HTTP/1.1.\n\nThe HTTP/1.1 handler in cowboy_http enforces the max_headers limit by counting the number of distinct header names in a map (maps:size(Headers)). When a request contains multiple header lines with the same name, the values are concatenated into a single ever-growing binary stored under that one map key (\", \" for regular headers, \"; \" for cookies), so the map size stays at one and the max_headers cap (default 100) is never reached. Because no accumulator bounds the total number of header lines or the total byte size of the header block (only per-line max_header_name_length and max_header_value_length apply), an unauthenticated client can send an arbitrary number of header lines with the same name and grow the connection process's binary memory to arbitrary size within the request window.\n\nThe impact per connection is bounded by request_timeout (default 5 seconds, not reset by header data), and by max_heap_size when set (the offending connection process is killed once its heap grows past the limit). When max_heap_size is left at the default (unset), sustained abuse can drive the Erlang VM into out-of-memory conditions.\n\nThis issue affects cowboy from 2.0.0-pre.4 before 2.18.0.","status":"published","published":"2026-07-28T12:31:20Z","modified":"2026-07-28T12:31:27Z","cvss":[{"version":"4.0","score":6.9,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"medium"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T15:09:51.995252Z"}],"nvd":[{"id":"CVE-2026-65624","description":"Allocation of Resources Without Limits or Throttling vulnerability in ninenines cowboy allows an unauthenticated remote attacker to exhaust connection process memory over HTTP/1.1.\n\nThe HTTP/1.1 handler in cowboy_http enforces the max_headers limit by counting the number of distinct header names in a map (maps:size(Headers)). When a request contains multiple header lines with the same name, the values are concatenated into a single ever-growing binary stored under that one map key (\", \" for regular headers, \"; \" for cookies), so the map size stays at one and the max_headers cap (default 100) is never reached. Because no accumulator bounds the total number of header lines or the total byte size of the header block (only per-line max_header_name_length and max_header_value_length apply), an unauthenticated client can send an arbitrary number of header lines with the same name and grow the connection process's binary memory to arbitrary size within the request window.\n\nThe impact per connection is bounded by request_timeout (default 5 seconds, not reset by header data), and by max_heap_size when set (the offending connection process is killed once its heap grows past the limit). When max_heap_size is left at the default (unset), sustained abuse can drive the Erlang VM into out-of-memory conditions.\n\nThis issue affects cowboy from 2.0.0-pre.4 before 2.18.0.","status":"published","published":"2026-07-28T10:16:50.5Z","modified":"2026-10-24T13:10:00.147Z","cvss":[{"version":"4.0","score":6.9,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"medium","assessor":"secondary"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T14:12:33.249634Z"}],"osv":[{"id":"CVE-2026-65624","title":"Cowboy HTTP/1.1 max_headers Bypass via Duplicate Header Names Enables Memory Exhaustion","description":"Allocation of Resources Without Limits or Throttling vulnerability in ninenines cowboy allows an unauthenticated remote attacker to exhaust connection process memory over HTTP/1.1.\n\nThe HTTP/1.1 handler in cowboy_http enforces the max_headers limit by counting the number of distinct header names in a map (maps:size(Headers)). When a request contains multiple header lines with the same name, the values are concatenated into a single ever-growing binary stored under that one map key (\", \" for regular headers, \"; \" for cookies), so the map size stays at one and the max_headers cap (default 100) is never reached. Because no accumulator bounds the total number of header lines or the total byte size of the header block (only per-line max_header_name_length and max_header_value_length apply), an unauthenticated client can send an arbitrary number of header lines with the same name and grow the connection process's binary memory to arbitrary size within the request window.\n\nThe impact per connection is bounded by request_timeout (default 5 seconds, not reset by header data), and by max_heap_size when set (the offending connection process is killed once its heap grows past the limit). When max_heap_size is left at the default (unset), sustained abuse can drive the Erlang VM into out-of-memory conditions.\n\nThis issue affects cowboy from 2.0.0-pre.4 before 2.18.0.","status":"published","published":"2026-07-28T10:01:01.811Z","modified":"2026-10-28T02:30:47.891809363Z","cvss":[{"version":"4.0","score":6.9,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","level":"medium"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T15:45:14.096824Z"},{"id":"DEBIAN-CVE-2026-65624","description":"Allocation of Resources Without Limits or Throttling vulnerability in ninenines cowboy allows an unauthenticated remote attacker to exhaust connection process memory over HTTP/1.1.  The HTTP/1.1 handler in cowboy_http enforces the max_headers limit by counting the number of distinct header names in a map (maps:size(Headers)). When a request contains multiple header lines with the same name, the values are concatenated into a single ever-growing binary stored under that one map key (\", \" for regular headers, \"; \" for cookies), so the map size stays at one and the max_headers cap (default 100) is never reached. Because no accumulator bounds the total number of header lines or the total byte size of the header block (only per-line max_header_name_length and max_header_value_length apply), an unauthenticated client can send an arbitrary number of header lines with the same name and grow the connection process's binary memory to arbitrary size within the request window.  The impact per connection is bounded by request_timeout (default 5 seconds, not reset by header data), and by max_heap_size when set (the offending connection process is killed once its heap grows past the limit). When max_heap_size is left at the default (unset), sustained abuse can drive the Erlang VM into out-of-memory conditions.  This issue affects cowboy from 2.0.0-pre.4 before 2.18.0.","status":"published","published":"2026-07-28T10:16:50.5Z","modified":"2026-10-25T09:47:34.578423928Z","cvss":[{"version":"4.0","score":6.9,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"medium"}],"updated_at":"2026-11-02T15:45:58.699079Z"},{"id":"EEF-CVE-2026-65624","title":"Cowboy HTTP/1.1 max_headers Bypass via Duplicate Header Names Enables Memory Exhaustion","description":"## Summary\n\nAllocation of Resources Without Limits or Throttling vulnerability in ninenines cowboy allows an unauthenticated remote attacker to exhaust connection process memory over HTTP/1.1.\n\nThe HTTP/1.1 handler in cowboy\\_http enforces the max\\_headers limit by counting the number of distinct header names in a map (maps:size(Headers)). When a request contains multiple header lines with the same name, the values are concatenated into a single ever-growing binary stored under that one map key (\", \" for regular headers, \"; \" for cookies), so the map size stays at one and the max\\_headers cap (default 100) is never reached. Because no accumulator bounds the total number of header lines or the total byte size of the header block (only per-line max\\_header\\_name\\_length and max\\_header\\_value\\_length apply), an unauthenticated client can send an arbitrary number of header lines with the same name and grow the connection process's binary memory to arbitrary size within the request window.\n\nThe impact per connection is bounded by request\\_timeout (default 5 seconds, not reset by header data), and by max\\_heap\\_size when set (the offending connection process is killed once its heap grows past the limit). When max\\_heap\\_size is left at the default (unset), sustained abuse can drive the Erlang VM into out-of-memory conditions.\n\nThis issue affects cowboy from 2.0.0-pre.4 before 2.18.0.","status":"published","published":"2026-07-28T10:01:01.811Z","modified":"2026-07-30T18:22:11.004772Z","cvss":[{"version":"4.0","score":6.9,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","level":"medium"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T15:46:33.520522Z"},{"id":"RHSA-2026:47231","title":"Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update","status":"published","published":"2026-07-29T10:11:41Z","modified":"2026-09-08T10:15:17Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:20.984762Z"},{"id":"RHSA-2026:47236","title":"Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update","status":"published","published":"2026-07-29T10:11:42Z","modified":"2026-09-07T10:15:32Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:20.984762Z"},{"id":"RHSA-2026:57882","title":"Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update","status":"published","published":"2026-08-21T10:14:11Z","modified":"2026-09-08T10:17:13Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:21.457353Z"},{"id":"UBUNTU-CVE-2026-65624","description":"Allocation of Resources Without Limits or Throttling vulnerability in ninenines cowboy allows an unauthenticated remote attacker to exhaust connection process memory over HTTP/1.1. The HTTP/1.1 handler in cowboy_http enforces the max_headers limit by counting the number of distinct header names in a map (maps:size(Headers)). When a request contains multiple header lines with the same name, the values are concatenated into a single ever-growing binary stored under that one map key (\", \" for regular headers, \"; \" for cookies), so the map size stays at one and the max_headers cap (default 100) is never reached. Because no accumulator bounds the total number of header lines or the total byte size of the header block (only per-line max_header_name_length and max_header_value_length apply), an unauthenticated client can send an arbitrary number of header lines with the same name and grow the connection process's binary memory to arbitrary size within the request window. The impact per connection is bounded by request_timeout (default 5 seconds, not reset by header data), and by max_heap_size when set (the offending connection process is killed once its heap grows past the limit). When max_heap_size is left at the default (unset), sustained abuse can drive the Erlang VM into out-of-memory conditions. This issue affects cowboy from 2.0.0-pre.4 before 2.18.0.","status":"published","published":"2026-07-28T10:16:00Z","modified":"2026-10-17T12:59:17.00705734Z","cvss":[{"version":"4.0","score":6.9,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","level":"medium"}],"updated_at":"2026-11-02T16:56:53.710209Z"},{"id":"AZL-94308","title":"CVE-2026-65624 affecting package rabbitmq-server for versions less than 3.13.7-9","description":"Allocation of Resources Without Limits or Throttling vulnerability in ninenines cowboy allows an unauthenticated remote attacker to exhaust connection process memory over HTTP/1.1.\n\nThe HTTP/1.1 handler in cowboy_http enforces the max_headers limit by counting the number of distinct header names in a map (maps:size(Headers)). When a request contains multiple header lines with the same name, the values are concatenated into a single ever-growing binary stored under that one map key (\", \" for regular headers, \"; \" for cookies), so the map size stays at one and the max_headers cap (default 100) is never reached. Because no accumulator bounds the total number of header lines or the total byte size of the header block (only per-line max_header_name_length and max_header_value_length apply), an unauthenticated client can send an arbitrary number of header lines with the same name and grow the connection process's binary memory to arbitrary size within the request window.\n\nThe impact per connection is bounded by request_timeout (default 5 seconds, not reset by header data), and by max_heap_size when set (the offending connection process is killed once its heap grows past the limit). When max_heap_size is left at the default (unset), sustained abuse can drive the Erlang VM into out-of-memory conditions.\n\nThis issue affects cowboy from 2.0.0-pre.4 before 2.18.0.","status":"published","published":"2026-07-28T10:16:50Z","modified":"2026-11-05T05:40:51Z","updated_at":"2026-11-05T16:41:26.077208Z"}]}}