{"answers":{"affected":"2 open source packages ship an affected version, including grpc and grpc_core. It affects 2 products.","exploited":"There is no known exploitation of CVE-2026-121808 in the wild and no public exploit code.","exposure":"","fix":"Upgrade grpc to 1.0.0 or later.","what":"CVE-2026-121808 is a high-severity vulnerability in elixir-grpc grpc, published on 13 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-121808 and fix it if it is affected.\n\nWhat it is: CVE-2026-121808 is a high-severity vulnerability in elixir-grpc grpc, published on 13 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-121808 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- grpc (Hex): affected from 0.4.0; fixed in 1.0.0\n- grpc_core (Hex): affected from 1.0.0; fixed in 1.1.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-121808/ (Markdown: https://insights.sbomify.com/CVE-2026-121808/index.md)","id":"CVE-2026-121808","markdown":"https://insights.sbomify.com/CVE-2026-121808/index.md","name":"CVE-2026-121808","record":{"aliases":["EEF-CVE-2026-121808","GHSA-xxp9-7hp4-rqwp"],"analysis":null,"analysis_generated_by":null,"assigner":"EEF","component":null,"cpe":[{"criteria":[{"cpe":"cpe:2.3:a:elixir-grpc:grpc:*:*:*:*:*:*:*:*","source":"cna","version_end_excluding":"1.0.0","version_start_including":"0.4.0"}],"n_criteria":1,"name":null,"product":"grpc","vendor":"elixir-grpc"},{"criteria":[{"cpe":"cpe:2.3:a:elixir-grpc:grpc_core:*:*:*:*:*:*:*:*","source":"cna","version_end_excluding":"1.1.0","version_start_including":"1.0.0"}],"n_criteria":1,"name":null,"product":"grpc_core","vendor":"elixir-grpc"}],"cvss":{"score":8.2,"severity":"high","source":"cna","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"},"cwes":[{"id":"CWE-409","name":"Improper Handling of Highly Compressed Data (Data Amplification)"}],"description":"Improper Handling of Highly Compressed Data (Data Amplification) vulnerability in elixir-grpc grpc_core and grpc allows unauthenticated attackers to exhaust server memory via a compressed Erlang external term in a gRPC message body.\n\nGRPC.Codec.Erlpack.decode/2 (grpc_core/lib/grpc/codec/erlpack.ex, and lib/grpc/codec/erlpack.ex before the package split) passes the message body to :erlang.binary_to_term/2. That function inflates a compressed term in full before it returns. The codec sets no limit on the decoded size, and its type checks run only on the decoded term. The server's max_body_size limit counts the compressed bytes of the request. A request with Content-Type: application/grpc+erlpack can therefore make the server allocate a term much larger than the request body.\n\nThis issue affects grpc_core: from 1.0.0 before 1.1.0; grpc: from 0.4.0 before 1.0.0.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Memory exhaustion via compressed Erlang terms in the elixir-grpc Erlpack codec","id":"CVE-2026-121808","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":null,"year":"2026"},"main_cpe":null,"main_fixed":["1.0.0"],"main_package":"grpc","n_packages":2,"n_references":6,"n_vendor_status":1,"next":{"headline":"CPU exhaustion via a truncated gRPC message on streaming RPCs in elixir-grpc grpc_server","id":"CVE-2026-121809"},"nickname":null,"packages":[{"ecosystem":"Hex","fixed":["1.0.0"],"introduced":["0.4.0"],"last_affected":[],"name_kind":null,"package":"grpc","purl":"pkg:hex/grpc","purl_source":"advisory","scope":"upstream","source":"EEF-CVE-2026-121808"},{"ecosystem":"Hex","fixed":["1.1.0"],"introduced":["1.0.0"],"last_affected":[],"name_kind":null,"package":"grpc_core","purl":"pkg:hex/grpc_core","purl_source":"advisory","scope":"upstream","source":"EEF-CVE-2026-121808"}],"prev":{"headline":"BIG-IP iRule Vulnerability","id":"CVE-2026-121805"},"products":["grpc","grpc_core"],"published":"2026-11-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Erlang Ecosystem Foundation","prefix":"EEF"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","text_fixes":[],"updated":"2026-11-19","vendor_status":[{"n_packages":2,"name":"Upstream","packages":[{"fixed":["1.0.0"],"introduced":["0.4.0"],"name":"grpc","purl":"pkg:hex/grpc","sources":["EEF-CVE-2026-121808"],"status":"fixed"},{"fixed":["1.1.0"],"introduced":["1.0.0"],"name":"grpc_core","purl":"pkg:hex/grpc_core","sources":["EEF-CVE-2026-121808"],"status":"fixed"}],"release":null,"scope":"upstream","status":"fixed","statuses":{"fixed":2},"vendor":null}],"vendors":["elixir-grpc"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-121808/"}