Quick answers
- Is CVE-2026-91855 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-91855 being exploited in the wild.
- How severe is CVE-2026-91855?
- Medium severity, with a CVSS score of 5.3, published 15 September 2026.
- Which products and versions are affected?
- Open5GS up to 2.7.7.
- Is there a fix for CVE-2026-91855?
- A patch was published on 2026-08-06: Fix commit 028e1dbb5e3271035ccee906ef417a97fc523f71 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-91855 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-91855?
- 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 an assertion failure (denial of service) in the PFCP Message Handler component (lib/pfcp/handler.c) affecting Open5GS up to version 2.7.7. The root cause is insufficient validation of the Outer Header Creation (OHC) IE (Information Element) in Create/Update FAR (Forwarding Action Rule) PFCP messages. Specifically, truncated or unsupported GTP-U/IPv6 IEs could be partially copied into a zero-initialized FAR structure, leaving incompletely initialized fields that later trigger an "Unknown family" assertion on subsequent requests. The attack is network-accessible and requires no authentication, as PFCP is a control-plane protocol exposed to the network. An attacker can craft malformed PFCP messages to crash the UPF (User Plane Function) or MME components. The fix (commit 028e1dbb5e3271035ccee906ef417a97fc523f71) validates OHC before copying and rejects invalid/unsupported variants.
Affected products
- Open5GS Open5GS up to 2.7.7
Timeline
- 2026-09-15: disclosed
- 2026-08-06: patched: Fix commit 028e1dbb5e3271035ccee906ef417a97fc523f71