cve.bz

CVE-2026-104591 Uncontrolled Resource Consumption

7.5 highEPSS 0.5%

High (7.5). EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
libosmocore through 1.14.1 contains a buffer overflow in osmo_iuup_compute_payload_crc() in src/gsm/iuup.c. This allows a remote attacker to cause a denial of service.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.5% (unchanged from 0.5% a week ago) estimated probability of exploitation activity in the next 30 days; 40th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-400 Uncontrolled Resource Consumption
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-104591 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-104591?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-104591?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-104591 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13libosmocoreno fix listedDEBIAN-CVE-2026-104591
Debian14libosmocore1.14.2-1DEBIAN-CVE-2026-104591
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 morelibosmocoreno fix listedUBUNTU-CVE-2026-104591
openSUSELeap 16.0libosmocore1.14.2-bp160.1.1openSUSE-SU-2026:22220-1
openSUSELeap 16.1libosmocore1.14.2-bp161.1.1openSUSE-SU-2026:22316-1
openSUSETumbleweedlibosmocore1.14.2-2.1openSUSE-SU-2026:12388-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated Important because unauthenticated remote network traffic can cause an immediate denial of service across systems utilizing libosmocore for cellular protocol handling. While the defect allows unauthenticated crashes over the network without user interaction, libosmocore is not included or supported in Red Hat Enterprise Linux products. Consequently, standard enterprise deployments are not exposed to this issue.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-104591.

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON