CVE-2026-104596: libosmocore out-of-bounds read in GSM 04.80 parser

CVE-2026-104596 · Severity: info · Published 2026-10-26

libosmocore is a library that handles mobile network telecommunications protocols, including GSM call and messaging features. A flaw in its supplementary-service parser allows attackers to read sensitive memory beyond buffer boundaries by sending crafted network messages, potentially exposing confidential information from the affected system.

Technologies: Osmocom Libosmocore. Vendors: Osmocom.

Quick answers

Is CVE-2026-104596 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-104596 being exploited in the wild.
How severe is CVE-2026-104596?
Informational severity, published 26 October 2026.
Which products and versions are affected?
Osmocom Libosmocore through 1.14.1.
Is there a fix for CVE-2026-104596?
A patch was published on 2026-10-26: Fix committed in git commit b6c8c72 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-104596 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-104596?
Check whether you run Osmocom Libosmocore at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

Out-of-bounds read vulnerabilities exist in the GSM 04.80 supplementary-service component parsers (parse_ss_invoke and parse_ss_return_result functions in src/gsm/gsm0480.c) due to off-by-one bounds checks and missing re-validation after optional field parsing. An attacker can craft malicious Facility component messages to trigger reads beyond allocated buffer limits or cause integer underflow in length calculations, potentially allowing information disclosure via memcpy operations.

Affected products

  • Osmocom libosmocore through 1.14.1

Timeline

  • 2026-10-26: disclosed
  • 2026-10-26: patched: Fix committed in git commit b6c8c72

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.