Unsafe Deserialization in grpc (CVE-2026-48853)
Summary
Vulnerability in grpc (CVE-2026-48853). Risk of unauthorized operations or information disclosure. Exploitable via Enum.map. Mitigation: upgrade to 1.0.0 or later.
Original description
The description as published by the source.
Summary
Deserialization of Untrusted Data and Allocation of Resources Without Limits or Throttling vulnerabilities in elixir-grpc grpc allow unauthenticated attackers to crash the BEAM node via atom table exhaustion and, when a decoded term flows into a call site that invokes it, achieve remote code execution on the server.
'Elixir.GRPC.Codec.Erlpack':decode/2 (lib/grpc/codec/erlpack.ex) calls :erlang.binary_to_term/1 on the raw gRPC message body without the :safe option, no size bound, and no type guard. Any unauthenticated peer that sends a request with Content-Type: application/grpc+erlpack can send a crafted payload that mints arbitrary new atoms (which are never garbage-collected, exhausting the bounded atom table and crashing the VM) or that encodes a fun term which, if applied anywhere downstream, executes attacker-controlled code inside the server process.
This issue affects grpc: from 0.4.0 before 1.0.0.
Configurations
GRPC.Codec.Erlpack must be explicitly registered as a codec on the gRPC server.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-48853 has been found in grpc.
Attackers can target a specific entry point like Enum.map over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade grpc to 1.0.0 or later.
If unsure, ask your IT team or search "grpc CVE-2026-48853" on the vendor's site.
CVE-2026-48853 (grpc) — CWE-502
Attack surface: Enum.map / Task.async / GRPC.Codec.Erlpack / codecs
Patched: 1.0.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Unsafe deserialization (CWE-502) exists in grpc. Attackers reach the vulnerable code path via Enum.map.
Check the vendor advisory for the affected versions of grpc. Attack surface: Enum.map / Task.async / GRPC.Codec.Erlpack / codecs.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.0.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'grpc' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'grpc' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
grpcを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade grpc to 1.0.0ステージング環境で 1.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Ubuntu UBUNTU-CVE-2026-48853 grpc
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- package hex.pm
- patch github.com
- web cna.erlef.org
- web osv.dev
- web github.com
- web github.com
- web github.com
- web github.com