Out of bounds read at smpp34_unpack()

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps Osmocom/libsmpp34 (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for Osmocom/libsmpp34.
2. 2Review the reported fix. Update Osmocom/libsmpp34 to 1.14.5 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

1. Published upstream

   Sep 18, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 18, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 18, 2026

Sources and claim methodology

• Source referencecgit.osmocom.org

Related CVEs

• Suricata smtp/mime: heap out-of-bounds read quoted-printable decoderAlso CWE-125
• FluidSynth: Heap Buffer Overflow in MIDI PlayerAlso CWE-125
• FluidSynth: Heap-based buffer overrun for DLS samplesAlso CWE-125
• Suricata ippair: hash collision can cause incorrect state reuse across IPv4 and IPv6Same generic ecosystem
• Suricata windows: unquoted LocalSystem service ImagePath can allow local privilege escalationSame generic ecosystem
• Suricata dhcp: unbounded transactions in unidirectional traffic can lead to resource exhaustionSame generic ecosystem