# CVE-2026-108105: Open5GS assertion failure in SGSN context request handling

Source: https://junglewise.ai/threats/cve-2026-108105-open5gs-through-2-8-0-contains-a-reachable-assertion  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-09. Updated: 2026-10-16  
License: CC BY 4.0 with a link back

CVE-2026-108105 · Severity: medium · CVSS 5.9 · Published 2026-10-09

Open5GS is a 5G and LTE core network implementation used to manage mobile subscriber traffic and connectivity. A vulnerability in its Mobility Management Entity (MME) component allows remote attackers to crash the service by sending malformed network packets, denying service to all mobile subscribers connected to the network.

Technologies: [Open5GS](https://junglewise.ai/threats/technologies/open5gs). Vendors: [Open5GS](https://junglewise.ai/threats/vendors/open5gs).

## Quick answers

**Is CVE-2026-108105 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-108105 being exploited in the wild.

**How severe is CVE-2026-108105?** Medium severity, with a CVSS score of 5.9, published 9 October 2026.

**Which products and versions are affected?** Open5GS through 2.8.0.

**Is there a fix for CVE-2026-108105?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-108105 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-108105?** Check whether you run Open5GS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

A reachable assertion vulnerability exists in the mme_gn_handle_sgsn_context_request() function when processing GTPv1-C packets with invalid SGSN Address Information Elements (IEs). Remote unauthenticated attackers with network access to the GN interface and knowledge of a valid SGSN address and subscriber IMSI/P-TMSI can trigger an assertion failure by supplying an invalid address length, crashing the open5gs-mmed process. A fix exists in versions after 2.8.0.

## Affected products

- Open5GS Open5GS through 2.8.0

## Timeline

- 2026-10-09: disclosed

## References

- [https://github.com/open5gs/open5gs](https://github.com/open5gs/open5gs)
- [https://github.com/open5gs/open5gs/blob/v2.8.0/src/mme/mme-gn-handler.c](https://github.com/open5gs/open5gs/blob/v2.8.0/src/mme/mme-gn-handler.c)

## Related threats

- [Open5GS HTTP/2 SBI server memory exhaustion](https://junglewise.ai/threats/cve-2026-106806-a-memory-exhaustion-issue-exists-in-open5gs-v2-8-0-in-the-http-2)
- [open5GS PFCP transaction handling denial of service](https://junglewise.ai/threats/cve-2026-106807-a-denial-of-service-vulnerability-exists-in-open5gs-v2-8-0-in)
- [Open5GS heap out-of-bounds write in multipart parsing](https://junglewise.ai/threats/cve-2026-116543-open5gs-1-3-0-through-2-8-0-contains-a-heap-out-of-bounds-write)
- [Open5GS heap out-of-bounds read in PFCP parsing](https://junglewise.ai/threats/cve-2026-108103-open5gs-through-2-8-0-contains-a-heap-out-of-bounds-read)
- [Open5GS heap out-of-bounds read in PFCP parsing](https://junglewise.ai/threats/cve-2026-108102-open5gs-through-2-8-0-contains-a-heap-out-of-bounds-read)