CVE-2026-104635
High 8.2No known exploitationFix availableUncontrolled recursion in elixir-protobuf/protobuf JSON decoding of self-referential messages
Record last updated
CVSS score
High on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
No EPSS score available
CISA remediation deadline
Not in the KEV catalog
Description
Uncontrolled Recursion vulnerability in Protobuf.JSON.Decode in elixir-protobuf protobuf allows an unauthenticated remote attacker to crash the decoding process via a deeply nested JSON document. Any application that decodes attacker-supplied JSON with Protobuf.JSON.decode/3, Protobuf.JSON.decode!/3, or Protobuf.JSON.from_decoded/3 into a schema that contains a self-referential or cyclic message type is affected. In lib/protobuf/json/decode.ex, the embedded-message clause of decode_singular/3 recurses into internal_from_json_data/3 once per nesting level without incrementing or checking the decoder's depth counter. The depth guard increase_depth_and_maybe_throw/1 covers only the Google.Protobuf.ListValue and Google.Protobuf.Struct clauses, so the recursion_limit option has no effect on user-defined message types. Each nesting level allocates a stack frame and heap objects, and a sufficiently deep document exhausts the memory of the decoding process. Confidentiality and integrity are not affected. This issue affects protobuf: from 0.8.0 before 0.17.1.
Weakness: CWE-674
Patching and mitigation
- Patch status
- Fix available (source: CVE record (EEF))
- Fix documented (source date)
- Mitigation
- Reject JSON documents whose nesting depth exceeds a fixed bound at the web or middleware layer before passing them to the decoder. No decoder option limits recursion for user-defined message types, so the check must happen before Protobuf.JSON.decode/3, Protobuf.JSON.decode!/3, or Protobuf.JSON.from_decoded/3 is called. Source (opens in a new tab)
- Vendor guidance
- github.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| elixir-protobuf | protobuf | from 0.8.0 before 0.17.1 | 0.17.1 | CVE Program |
| elixir-protobuf | protobuf | from b0a1d4eaffaf50012fa71a8e931a47cf252d0370 before e9432ad1c4099511905353cebcececa3a1f7c3ff | e9432ad1c4099511905353cebcececa3a1f7c3ff | CVE Program |
Timeline
Disclosure
CVE record published by EEF
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (EEF)
Vendor guidance and references
- Fix commit e9432ad in elixir-protobuf/protobuf (opens in a new tab)patch
- GitHub Advisory (opens in a new tab)related, vendor-advisory
- EEF CNA record for CVE-2026-104635 (opens in a new tab)related
- Introducing commit b0a1d4e in elixir-protobuf/protobuf (opens in a new tab)related
- OSV record EEF-CVE-2026-104635 (opens in a new tab)related