# CVE-2026-121808: Memory exhaustion via compressed Erlang terms in the elixir-grpc Erlpack codec


- **Severity:** High 8.2 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 13 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** EEF-CVE-2026-121808, GHSA-xxp9-7hp4-rqwp

## What is CVE-2026-121808?

CVE-2026-121808 is a high-severity vulnerability in elixir-grpc grpc, published on 13 Nov 2026. 

### Official 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.

GRPC.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.

This issue affects grpc_core: from 1.0.0 before 1.1.0; grpc: from 0.4.0 before 1.0.0.

Weakness: CWE-409 (Improper Handling of Highly Compressed Data (Data Amplification))

## Which versions are affected by CVE-2026-121808?

2 open source packages ship an affected version, including grpc and grpc_core. It affects 2 products.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `grpc` | Hex | `pkg:hex/grpc` | From 0.4.0 | 1.0.0 |
| `grpc_core` | Hex | `pkg:hex/grpc_core` | From 1.0.0 | 1.1.0 |

Products: Elixir-Grpc Grpc, Elixir-Grpc Grpc Core.

CPE match criteria (CPE 2.3):

- `cpe:2.3:a:elixir-grpc:grpc:*:*:*:*:*:*:*:*` from 0.4.0 before 1.0.0
- `cpe:2.3:a:elixir-grpc:grpc_core:*:*:*:*:*:*:*:*` from 1.0.0 before 1.1.0

Status by vendor (upstream, then each distribution release and vendor build):

| Who | Release | Status | Packages | Fixed in |
| --- | --- | --- | --- | --- |
| Upstream |  | fixed | `grpc`, `grpc_core` | 1.0.0, 1.1.0 |

## How do I fix CVE-2026-121808?

Upgrade grpc to 1.0.0 or later.

## Is CVE-2026-121808 being exploited?

There is no known exploitation of CVE-2026-121808 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-121808 and fix it if it is affected.

What it is: CVE-2026-121808 is a high-severity vulnerability in elixir-grpc grpc, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-121808 in the wild and no public exploit code.

Affected packages and fixed versions:
- grpc (Hex): affected from 0.4.0; fixed in 1.0.0
- grpc_core (Hex): affected from 1.0.0; fixed in 1.1.0

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-121808/ (Markdown: https://insights.sbomify.com/CVE-2026-121808/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-121808
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-121808
- OSV: https://osv.dev/vulnerability/CVE-2026-121808

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-121808/
Summaries are generated and may contain mistakes; the official description above is the record.
