Live › vulnerability › CVE-2026-106807
Open5GS 2.8.0 mishandles a failed PFCP transaction allocation, which trips an assertion and aborts the network function process. An attacker who can send PFCP messages to the SMF or UPF can exhaust transaction resources and knock the service offline until it is restarted.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-02 17:24 UTC. All times on this page are UTC.
Operators running Open5GS 2.8.0 as a 5G core SMF or UPF that accepts PFCP messages from peers reachable over the network. Systems not running Open5GS, or not exposing PFCP beyond trusted core elements, can likely skip it.
No product ranges from the sources yet.
open5gs-smfd --version or check the installed Open5GS version on SMF and UPF hosts, expecting 2.8.0 to be affected.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
A denial-of-service vulnerability exists in open5GS v2.8.0 in the PFCP transaction handling path. When the PFCP transaction or timer resource pool is exhausted, ogs_pfcp_xact_remote_create() returns NULL, but the failure is not handled properly and leads to an ogs_assert(new) failure in ogs_pfcp_xact_receive(). An attacker able to send PFCP messages to the affected SMF/UPF can exhaust transaction resources and cause the network function process to terminate with SIGABRT, resulting in service disruption and preventing further session establishment until the affected component is restarted.
This page as .md · .json · in your agent: get_signal("CVE-2026-106807")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.