Advisory

GHSA-85rr-4rh9-hhwh

Also known as: CVE-2020-26243, PYSEC-2026-684

Summary

Memory leak in Nanopb

Details

Impact
Decoding specifically formed message can leak memory if dynamic allocation is enabled and an oneof field contains a static submessage that contains a dynamic field, and the message being decoded contains the submessage multiple times. This is rare in normal messages, but it is a concern when untrusted data is parsed.

Patches
Preliminary patch is available on git and problem will be patched in versions 0.3.9.7 and 0.4.4 once testing has been completed.

Workarounds
Following workarounds are available:

  • Set the option no_unions for the oneof field. This will generate fields as separate instead of C union, and avoids triggering the problematic code.
  • Set the type of the submessage field inside oneof to FT_POINTER. This way the whole submessage will be dynamically allocated and the problematic code is not executed.
  • Use an arena allocator for nanopb, to make sure all memory can be released afterwards.

References
Bug report: https://github.com/nanopb/nanopb/issues/615

For more information
If you have any questions or comments about this advisory, comment on the bug report linked above.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2020-11-25 16:53 UTC
Modified
2026-07-08 06:00 UTC

Affected packages and fixes

nanopb

PyPI · All systems

Affected

  • introduced 0.3.2, fixed 0.3.9.7 (ecosystem)

Fixed versions

0.3.9.7

Fix

  • Fixed version 0.3.9.7
    pip install --upgrade nanopb==0.3.9.7

nanopb

PyPI · All systems

Affected

  • introduced 0.4.0, fixed 0.4.4 (ecosystem)

Fixed versions

0.4.4

Fix

  • Fixed version 0.4.4
    pip install --upgrade nanopb==0.4.4

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences