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.
CVE-2026-54451
HIGHPre-NVD 8.28.2Trending — 3 sources updated this week
EchelonGraph scoreLOW confidence
This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: secondary
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.2
- EG Score
- 8.2(low)
- EG Risk
- 41(Track)EG Risk 41/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity82% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 23%
- KEV
- Not listed
Published
July 15, 2026
Last Modified
September 17, 2026
Advisory Details (3)
Auto-updated Sep 17, 2026🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github_commit
commit b8efa97790ee (elixir-protobuf/protobuf)
Fix landed in elixir-protobuf/protobuf commit b8efa97790ee — awaiting tagged release
https://github.com/elixir-protobuf/protobuf/commit/b8efa97790eece3d2d0e8e7c31a45ed409fe5338github_commit
commit 352d1769a0ef (elixir-protobuf/protobuf)
Fix landed in elixir-protobuf/protobuf commit 352d1769a0ef — awaiting tagged release
https://github.com/elixir-protobuf/protobuf/commit/352d1769a0ef575a8d18c3f9620609efdb73e2bcgithub Patch Available🟡 PoC Available
Unbounded recursion depth in embedded-message decoding · Advisory · elixir-protobuf/protobuf · GitHub
https://github.com/elixir-protobuf/protobuf/security/advisories/GHSA-rv48-qqj5-crxgVendor Advisories for CVE-2026-54451(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Hex(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| protobuf | 0.10.0 ... 0.9.0 (10 versions) | 0.16.1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 19:28 UTCEG score recompute
- 2026-09-17 18:29 UTCEG score recompute▲ 8.20
- 2026-09-17 18:29 UTCMITRE cvelistV5CVSS v3 → 8.2 · CVSS v4 → 8.2
- 2026-08-01 20:44 UTCEG score recompute
- 2026-07-26 11:33 UTCEG score recompute
- 2026-07-23 03:19 UTCEG score recompute
- 2026-07-15 17:54 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-54451?
CVE-2026-54451 is a high vulnerability published on July 15, 2026. 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,…
When was CVE-2026-54451 disclosed?
CVE-2026-54451 was first published in the National Vulnerability Database on July 15, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54451 actively exploited?
CVE-2026-54451 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 77.0% of all scored CVEs.
What is the CVSS score of CVE-2026-54451?
CVE-2026-54451 has a CVSS v3 base score of 8.2 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-54451?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54451, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54451
Is Your Infrastructure Affected by CVE-2026-54451?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.