CVE-2026-48854
Memory exhaustion in elixir-grpc due to unbounded reads; slow-trickle requests can crash node.
Is CVE-2026-48854 being exploited?
Not confirmed. CVE-2026-48854 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.34% probability of exploitation in the next 30 days.
How severe is CVE-2026-48854?
CVE-2026-48854 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-48854?
Yes. A fix has been recorded for CVE-2026-48854. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-48854 affect?
CVE-2026-48854 affects elixir-grpc <1.0.0 (>=0.3.1). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-48854?
Upgrade to elixir-grpc 1.0.0 or later
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker can exhaust BEAM memory by streaming large or slow gRPC requests, crashing the server.
Patch when possible
- affected>= 0.3.1 and < 1.0.0
- affected>= d1abe70a6cad6dac4a3f8235d883d7c896989560 and < 49e18c3ec6bb9afe2f712caad3dbab5c56a68a00
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.