# CVE-2026-75894: Reachable assertion at ranap_handle_co_dt()

> A reachable assertion in osmo-iuh allows remote attackers to cause a process crash and denial of service via a maliciously sized NAS-PDU.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-75894, GHSA-g4v5-w6q6-j5cq, UBUNTU-CVE-2026-75894, openSUSE-SU-2026:21954-1

## What is CVE-2026-75894?

CVE-2026-75894 is a high-severity denial of service vulnerability in Osmocom osmo-iuh, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In osmo-iuh from 0.1.0 through 1.8.0 a reachable assertion was found in the ranap_handle_co_dt() function via a arbitrarily sized NAS-PDU that leads to process crash and remote denial of service.

Weakness: CWE-617 (Reachable Assertion)

## Which versions are affected by CVE-2026-75894?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `osmo-iuh` | openSUSE:Leap 16.0 | All versions | 1.5.1-bp160.2.1 |

## How do I fix CVE-2026-75894?

Apply the vendor's patch.

## Is CVE-2026-75894 being exploited?

There is no known exploitation of CVE-2026-75894 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-75894 and fix it if it is affected.

What it is: CVE-2026-75894 is a high-severity denial of service vulnerability in Osmocom osmo-iuh, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-75894 in the wild and no public exploit code.

Affected product: Osmocom osmo-iuh. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-75894/ (Markdown: https://insights.sbomify.com/CVE-2026-75894/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-75894
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-75894
- OSV: https://osv.dev/vulnerability/CVE-2026-75894

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-75894/
Summaries are generated and may contain mistakes; the official description above is the record.