{"affected":[{"defaultStatus":"unaffected","ecosystem":"hex","packageName":"grpc_server","product":"grpc_server","source":"CNA: EEF","vendor":"elixir-grpc","versions":[{"lessThan":"1.0.6","status":"affected","version":"1.0.0","versionType":"semver"}]},{"defaultStatus":"unaffected","ecosystem":"github","packageName":"elixir-grpc/grpc","product":"grpc_server","source":"CNA: EEF","vendor":"elixir-grpc","versions":[{"lessThan":"0b663ca53dbf0f36f7f67ff1d0026f4482a18915","status":"affected","version":"49e18c3ec6bb9afe2f712caad3dbab5c56a68a00","versionType":"git"}]}],"cveId":"CVE-2026-71397","cwes":["CWE-770"],"description":"Allocation of Resources Without Limits or Throttling vulnerability in elixir-grpc grpc_server allows unauthenticated attackers to exhaust memory and crash the node via an oversized client-streaming or bidirectional-streaming request body.\n\nThe streaming read clause of 'Elixir.GRPC.Server.Adapters.Cowboy.Handler':info/3 (grpc_server/lib/grpc/server/adapters/cowboy/handler.ex) never checks the configured max_body_size. Only the unary read path enforces that cap. 'Elixir.GRPC.Server.Adapters.Cowboy':reading_stream/1 (grpc_server/lib/grpc/server/adapters/cowboy.ex) appends every received chunk to its buffer until a complete length-prefixed message arrives. A client can declare a very large message and send it across many small HTTP/2 DATA frames, and the server buffers all of it.\n\nThis issue affects grpc_server: from 1.0.0 before 1.0.6.","epss":null,"exploits":[],"kev":null,"metrics":[{"score":8.2,"severity":"high","source":"CNA: EEF","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"}],"modifiedAt":1793998923676,"publishedAt":1793998923676,"references":[{"source":"CNA: EEF","tags":["vendor-advisory","related"],"url":"https://github.com/elixir-grpc/grpc/security/advisories/GHSA-vx6q-cr5q-945g"},{"source":"CNA: EEF","tags":["related"],"url":"https://cna.erlef.org/cves/CVE-2026-71397.html"},{"source":"CNA: EEF","tags":["related"],"url":"https://osv.dev/vulnerability/EEF-CVE-2026-71397"},{"source":"CNA: EEF","tags":["related"],"url":"https://github.com/elixir-grpc/grpc/commit/49e18c3ec6bb9afe2f712caad3dbab5c56a68a00"},{"source":"CNA: EEF","tags":["patch"],"url":"https://github.com/elixir-grpc/grpc/commit/0b663ca53dbf0f36f7f67ff1d0026f4482a18915"}],"remediation":[{"kind":"fix","source":"CNA: EEF","text":"The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.","url":"https://github.com/elixir-grpc/grpc/commit/0b663ca53dbf0f36f7f67ff1d0026f4482a18915"}],"revision":"c94c67584bd6673a13611e924f4a3180999bf982f9e9b52123751875088a9619","sources":[{"modifiedAt":1793998923676,"name":"CNA: EEF","retrievedAt":1794002938620,"url":"https://www.cve.org/CVERecord?id=CVE-2026-71397"}],"ssvc":null,"status":"published","title":"Unbounded request body accumulation on streaming RPCs causes memory exhaustion in grpc_server","updatedAt":1794002938620}