---
id: "CVE-2026-104597"
kind: "vulnerability"
aliases: ["CVE-2026-104597"]
title: "libosmocore: out-of-bounds read in IuUP receive lets remote attackers leak memory"
severity: "unknown"
cvss: null
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["libosmocore", "osmocom", "package", "self-hosted", "telecom"]
not_affected_if: ["no-libosmocore"]
published_at: "2026-10-26T20:17:37+00:00"
first_seen_at: "2026-10-26T20:50:17+00:00"
updated_at: "2026-10-26T20:52:02+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-104597", "first_seen_at": "2026-10-26T20:50:17+00:00"}]
---

# libosmocore: out-of-bounds read in IuUP receive lets remote attackers leak memory

libosmocore through 1.14.1 has an out-of-bounds read in iuup_rx_initialization() in src/gsm/iuup.c. A remote attacker can use it to obtain sensitive information from process memory.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed libosmocore version with `pkg-config --modversion libosmocore` and compare it to `1.14.1`
- Look for `iuup.c` or `libosmocore` in the dependency tree of any cellular or GSM tooling you run (unknown otherwise)

## Fix

- Upgrade libosmocore past `1.14.1` once a fixed release is published (unknown whether one exists yet)

## Timeline

- 2026-10-26T20:50:17+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-104597

## From the sources

libosmocore through 1.14.1 contains an out-of-bounds read in iuup_rx_initialization() in src/gsm/iuup.c. This allows a remote attacker to obtain sensitive information.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_