Skip to main content
No exploitation reportedFix available

CVE-2024-53984

No exploitation reported by the sources we read.

  • Published2024-12-02
  • WeaknessCWE-401 · CWE-755

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Nanopb is a small code-size Protocol Buffers implementation. When the compile time option PB_ENABLE_MALLOC is enabled, the message contains at least one field with FT_POINTER field type, custom stream callback is used with unknown stream length. and the pb_decode_ex() function is used with flag PB_DECODE_DELIMITED, then the pb_decode_ex() function does not automatically call pb_release(), like is done for other failure cases. This could lead to memory leak and potential denial-of-service. This vulnerability is fixed in 0.4.9.1.

Timeline

dates in UTC
  1. 2024-12-0216:15CVE publishedNVD

Versions per branch

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • nanopb
    Affected
    • = >=0.4.0, < 0.4.9.1no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2024-12-02

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • nanopbUbuntu:Pro:20.04:LTSall versions · no fixed version listed
  • nanopbUbuntu:26.10all versions · no fixed version listed
  • nanopbUbuntu:26.04:LTSall versions · no fixed version listed
  • nanopbUbuntu:25.10all versions · no fixed version listed
  • nanopbUbuntu:24.04:LTSall versions · no fixed version listed
  • nanopbUbuntu:22.04:LTSall versions · no fixed version listed
  • nanopbSUSE:Package Hub 15 SP6all versions · fixed in 0.4.6-bp156.4.3.1
  • nanopbopenSUSE:Leap 15.6all versions · fixed in 0.4.6-bp156.4.3.1

3 more package ranges on OSV.dev

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVE recordread 2026-10-23
  • CISA-ADPSSVC decisionnone2024-12-02
  • CNACVSS 3.14.3known since 2026-10-23
  • CNAweakness (CWE)CWE-401, CWE-755known since 2026-10-23
  • FIRST EPSSEPSS score0.4 %2026-11-09
  • OSVaffected packages—

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
Published
2024-12-02
Last Modified
2026-06-17
NVD status
Deferred

Frequently asked questions

What is CVE-2024-53984?

Nanopb is a small code-size Protocol Buffers implementation. When the compile time option PB_ENABLE_MALLOC is enabled, the message contains at least one field with FT_POINTER field type, custom stream callback is used with unknown stream length. and the pb_decode_ex() function is used with flag PB_DECODE_DELIMITED, then the pb_decode_ex() function does not automatically call pb_release(), like is done for other failure cases. This could lead to memory leak and potential denial-of-service. This vulnerability is fixed in 0.4.9.1.

Is CVE-2024-53984 actively exploited?

Active exploitation of CVE-2024-53984 has not been confirmed. Its EPSS score was 0.4% on 2026-11-09, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2024-53984?

CVE-2024-53984 has a CVSS v3 base score of 4.3 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L.

Running nanopb? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record