# CVE-2026-104594: libosmocore out-of-bounds read in IPA CCM identity-tag parsing

Source: https://junglewise.ai/threats/cve-2026-104594-libosmocore-through-1-14-1-contains-out-of-bounds-reads-in-the  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-26. Updated: 2026-10-26  
License: CC BY 4.0 with a link back

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

libosmocore is a core library for GSM/cellular network operations used in mobile infrastructure software. An out-of-bounds read vulnerability in its IPA CCM identity-tag parsers allows a remote attacker to read sensitive data from memory, potentially exposing network configuration, credentials, or other confidential information processed by the affected system.

Technologies: [Osmocom Libosmocore](https://junglewise.ai/threats/technologies/libosmocore). Vendors: [Osmocom](https://junglewise.ai/threats/vendors/osmocom).

## Quick answers

**Is CVE-2026-104594 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-104594 being exploited in the wild.

**How severe is CVE-2026-104594?** 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-104594?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-104594 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-104594?** 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

The vulnerability exists in ipa_ccm_id_get_parse() and ipa_ccm_id_resp_parse() functions in src/gsm/ipa.c, where zero-length TLV tags bypass length validation and cause integer underflow (t_len - 1 on a uint16_t becomes 65535), allowing out-of-bounds buffer reads. Additionally, unbounded format strings in logging functions read past uninitialized memory. A remote attacker can send crafted IPA protocol messages to trigger these reads.

## Affected products

- osmocom libosmocore through 1.14.1

## Timeline

- 2026-10-26: disclosed

## References

- [https://github.com/osmocom/libosmocore/commit/325ffb5204d7e1659ca2fec3b2f14c33b969ee71](https://github.com/osmocom/libosmocore/commit/325ffb5204d7e1659ca2fec3b2f14c33b969ee71)
- [https://github.com/osmocom/libosmocore/commit/8ba652bca2f28ec05ff5979846199e2c46657633](https://github.com/osmocom/libosmocore/commit/8ba652bca2f28ec05ff5979846199e2c46657633)

## Related threats

- [libosmocore out-of-bounds read in IuUP initialization](https://junglewise.ai/threats/cve-2026-104597-libosmocore-through-1-14-1-contains-an-out-of-bounds-read-in)
- [libosmocore out-of-bounds read in GSM 04.80 parser](https://junglewise.ai/threats/cve-2026-104596-libosmocore-through-1-14-1-contains-out-of-bounds-reads-in-the)
- [libosmocore out-of-bounds read in CBSP decoder](https://junglewise.ai/threats/cve-2026-104592-libosmocore-through-1-14-1-contains-an-out-of-bounds-read-in-the)
- [libosmocore buffer overflow in osmo_iuup_compute_payload_crc()](https://junglewise.ai/threats/cve-2026-104591-libosmocore-through-1-14-1-contains-a-buffer-overflow-in-osmo)
