# CVE-2026-30047: Open5GS reachable assertion in SM context handling

Source: https://junglewise.ai/threats/cve-2026-30047-open5gs-reachable-assertion-in-sm-context-handling  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-08-27. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-30047 · Severity: high · CVSS 7.5 · Published 2026-08-27

Open5GS is a core component of 5G mobile networks that manages packet data sessions between user devices and the internet. A vulnerability in the session management component allows a remote attacker to crash the service by sending a specially crafted network request, disrupting mobile network operations and preventing users from accessing data services.

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

## Quick answers

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

**How severe is CVE-2026-30047?** High severity, with a CVSS score of 7.5, published 27 August 2026.

**Which products and versions are affected?** Open5GS v2.7.6.

**Is there a fix for CVE-2026-30047?** 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-30047 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-30047?** 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 /nsmf-pdusession/v1/sm-contexts component of Open5GS v2.7.6. The vulnerability is triggered in the smf_sess_find_by_psi() function when a DELETE request is sent with an unassigned PDU session identity (psi). The function fails an internal consistency check (assertion) that expects a valid session identifier, causing the SMF daemon to abort. An unauthenticated remote attacker can trigger this crash over the network by crafting a malicious HTTP/2 request to the session management endpoint, leading to Denial of Service. The fix requires patching the assertion handling or request validation logic in the vulnerable function.

## Affected products

- Open5GS Open5GS v2.7.6

## Timeline

- 2026-08-27: disclosed: CVE-2026-30047 published on NVD

## References

- [https://github.com/open5gs/open5gs/issues/4201](https://github.com/open5gs/open5gs/issues/4201)

## 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 assertion failure in SGSN context request handling](https://junglewise.ai/threats/cve-2026-108105-open5gs-through-2-8-0-contains-a-reachable-assertion)
- [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)