# CVE-2026-108105: Open5GS through 2.8.0 MME Reachable Assertion via GTPv1 SGSN Context Request

> Remote attackers can crash the Open5GS MME by sending malformed GTPv1-C packets, causing a denial of service for all subscribers.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2026
- **Updated:** 9 Oct 2026
- **Also known as:** GHSA-9crh-64c8-56q6, GHSA-ch22-9c64-r8wh

## What is CVE-2026-108105?

CVE-2026-108105 is a high-severity denial of service vulnerability in open5gs, published on 9 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Open5GS through 2.8.0 contains a reachable assertion vulnerability in mme_gn_handle_sgsn_context_request() that allows remote unauthenticated attackers to crash the MME via malformed SGSN Address IEs. Attackers sending GTPv1-C traffic from a configured SGSN address with a known UE IMSI or P-TMSI can supply an invalid address length to terminate open5gs-mmed, denying service to all subscribers.

Weakness: CWE-617 (Reachable Assertion)

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


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

No fix has been published for CVE-2026-108105 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-108105 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-108105 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108105 is a high-severity denial of service vulnerability in open5gs, published on 9 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-108105 exists.

Affected product: open5gs. 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-108105/ (Markdown: https://insights.sbomify.com/CVE-2026-108105/index.md)
```

## Sources

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

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