Nanopb is a lightweight protocol-buffer encoder and decoder library designed for embedded and resource-constrained systems, where it sees widespread integration across IoT, embedded firmware, and real-time applications. The observed vulnerability surface concentrates on input-parsing and memory-safety weaknesses including improper input validation, buffer boundary violations, and invalid pointer dereferences—typical of libraries that process untrusted binary data in memory-limited environments. Current severity, exploitation activity, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Nanopb Project over time
Signals from CVEs in this vendor scope (4 CVEs).
4 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2020-5235CRITICAL There is a potentially exploitable out of memory condition In Nanopb before 0.4.1, 0.3.9.5, and 0.2.9.4. When nanopb is compiled with PB_ENABLE_MALLOC, the message to be decoded co | Feb 4, 2020 | 9.8 | 29 | NO | NO |
CVE-2014-125106CRITICAL Nanopb before 0.3.1 allows size_t overflows in pb_dec_bytes and pb_dec_string. | Jun 17, 2023 | 9.8 | 28 | NO | NO |
CVE-2020-26243HIGH Nanopb is a small code-size Protocol Buffers implementation. In Nanopb before versions 0.4.4 and 0.3.9.7, decoding specifically formed message can leak memory if dynamic allocation | Nov 25, 2020 | 7.5 | 24 | NO | NO |
CVE-2021-21401HIGH Nanopb is a small code-size Protocol Buffers implementation in ansi C. In Nanopb before versions 0.3.9.8 and 0.4.5, decoding a specifically formed message can cause invalid `free() | Mar 23, 2021 | 7.1 | 22 | NO | NO |
Signals from CVEs in this vendor scope (4 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Nanopb Project.
Media articles that mention a CVE ID that affects a product developed by Nanopb Project — matched by CVE ID, not by vendor name.