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