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