Is CVE-2026-104597 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-104597 being exploited in the wild.

How severe is CVE-2026-104597?

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-104597?

Yes: fixed in 1.14.2 and later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-104597 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-104597?

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.

CVE-2026-104597: libosmocore out-of-bounds read in IuUP initialization

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

libosmocore is a core library for mobile telecommunications infrastructure that implements IuUP protocol handling. An out-of-bounds memory read vulnerability in the IuUP initialization message processing could allow a remote attacker to read sensitive data from memory without authentication.

Technologies: Osmocom Libosmocore. Vendors: Osmocom.

Quick answers

Is CVE-2026-104597 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-104597 being exploited in the wild.
How severe is CVE-2026-104597?: 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-104597?: Yes: fixed in 1.14.2 and later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-104597 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-104597?: 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.

How to fix

Fixed in: 1.14.2 and later

Technical details

An out-of-bounds read exists in the iuup_rx_initialization() function in src/gsm/iuup.c due to incomplete input length validation marked as TODO in the code. A remote attacker can send a specially crafted IuUP initialization message to trigger the OOB read and disclose sensitive information from adjacent memory regions.

Affected products

osmocom libosmocore through 1.14.1

Timeline

2026-10-26: disclosed: CVE-2026-104597 published
2026-10-26: patched: Fix committed validating msgb input length in IuUP rx initialization path

References

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