Vulnerability Description
Elixir protobuf is a pure Elixir implementation of Google Protobuf. From 0.8.0 until 0.16.1, services that decode attacker-controlled protobuf bytes with Protobuf.Decoder can be taken offline when the schema contains a self-referential or cyclic message type. In lib/protobuf/decoder.ex, Protobuf.Decoder.value_for_field/3 handles an embedded?: true field by recursively entering the decode / build_message / handle_value / value_for_field call chain without enforcing a nesting-depth limit. Deeply nested embedded fields retain non-tail recursive frames, allowing a comparatively small request to consume substantial CPU and memory, pin a BEAM scheduler, and exhaust the node. This issue is fixed in version 0.16.1.
Related Weaknesses (CWE)
References
- https://github.com/elixir-protobuf/protobuf/commit/352d1769a0ef575a8d18c3f962060
- https://github.com/elixir-protobuf/protobuf/commit/b8efa97790eece3d2d0e8e7c31a45
- https://github.com/elixir-protobuf/protobuf/releases/tag/v0.16.1
- https://github.com/elixir-protobuf/protobuf/security/advisories/GHSA-rv48-qqj5-c
FAQ
What is CVE-2026-54451?
CVE-2026-54451 is a documented vulnerability. Elixir protobuf is a pure Elixir implementation of Google Protobuf. From 0.8.0 until 0.16.1, services that decode attacker-controlled protobuf bytes with Protobuf.Decoder can be taken offline when the...
How severe is CVE-2026-54451?
CVSS scoring is not yet available for CVE-2026-54451. Check NVD for updates.
Is there a patch for CVE-2026-54451?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.