# CVE-2026-92417: Open5GS null pointer dereference in PFCP handler

Source: https://junglewise.ai/threats/cve-2026-92417-open5gs-null-pointer-dereference-in-pfcp-handler  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-16. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-92417 · Severity: medium · CVSS 6.5 · Published 2026-09-16

Open5GS is an open-source implementation of a 5G core network that processes telecommunications signaling protocols. A vulnerability in its PFCP (Packet Forwarding Control Protocol) parser can cause a service crash when processing malformed network packets, disrupting mobile network operations and affecting all connected devices.

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

## Quick answers

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

**How severe is CVE-2026-92417?** Medium severity, with a CVSS score of 6.5, published 16 September 2026.

**Which products and versions are affected?** Open5GS up to 2.8.0.

**Is there a fix for CVE-2026-92417?** A patch was published on 2026-09-10: Patch commit 8f07b507b78ff94776f2cd49276eb116ed93d7f2 applied Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

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

**Am I affected by CVE-2026-92417?** 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

The vulnerability is a null pointer dereference in the PFCP packet parser, specifically in the ogs_pfcp_parse_volume_measurement() function within lib/pfcp/types.c. The parser reads flag octets and 8-octet fields without validating the declared IE (Information Element) length, allowing reads up to 48 octets past the end of a malformed IE. Additionally, SMF usage report handlers call this function without checking the volume_measurement.presence field, leading to NULL dereference on absent IEs. An attacker on the network can send a crafted PFCP packet with truncated or malformed Information Elements to trigger the crash. The patch (commit 8f07b507b78ff94776f2cd49276eb116ed93d7f2) adds bounds checks to validate octet length before parsing.

## Affected products

- Open5GS Open5GS up to 2.8.0

## Timeline

- 2026-09-16: disclosed
- 2026-09-10: patched: Patch commit 8f07b507b78ff94776f2cd49276eb116ed93d7f2 applied

## References

- [https://github.com/open5gs/open5gs/](https://github.com/open5gs/open5gs/)
- [https://github.com/open5gs/open5gs/commit/8f07b507b78ff94776f2cd49276eb116ed93d7f2](https://github.com/open5gs/open5gs/commit/8f07b507b78ff94776f2cd49276eb116ed93d7f2)

## 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)