VulnerabilityPublished 26 Oct 2026

CVE-2026-104591: libosmocore through 1.14.1 contains a buffer overflow in osmo_iuup_compute_payload_crc() in

Source CVE Database V5

Not known to be exploited.

Data as of 26 Oct 2026, 19:42 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Affects: libosmocore through 1.14.1

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Description

A buffer overflow vulnerability exists in libosmocore through version 1.14.1 within the function osmo_iuup_compute_payload_crc() located in src/gsm/iuup.c. This flaw allows a remote attacker to cause a denial of service condition.

Impact

The vulnerability enables a remote attacker to cause a denial of service, likely by triggering a crash due to the buffer overflow. There is no information about code execution or data corruption beyond the denial of service impact.

Summary

libosmocore versions up to and including 1.14.1 contain a buffer overflow vulnerability in the osmo_iuup_compute_payload_crc() function. This function is part of the GSM IUUP protocol implementation. Exploitation of this vulnerability can lead to a denial of service by crashing the affected process. No further details on exploitation methods or additional impacts are provided.

References

Community reviews

Loading reviews…