CVE-2026-106807

Published Nov 2, 2026 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The vulnerability in open5GS version 2.8.0 permits an attacker who can send PFCP messages to exhaust transaction resources. The code fails to check the return value of ogs_pfcp_xact_remote_create() and later triggers an assertion that crashes the process with SIGABRT. The result is a denial of service that stops the SMF/UPF from handling new sessions until the component is restarted.

Affected Systems

Affected systems are deployments of the open5GS open source 5G core network that run the SMF or UPF components with the 2.8.0 release. No other versions or vendors were identified in the CNA data.

Risk and Exploitability

The vulnerability is exploitable by any actor who can reach the SMF/UPF PFCP interface, which is typically reachable over an internal network. Based on the description, it is inferred that the attack path involves sending crafted PFCP messages to drain transaction or timer pools, allowing the attacker to induce a crash without special privileges on the target system. The EPSS score of < 1% and the absence of a KEV listing suggest a low likelihood of exploitation, but the CVSS score of 5.3 indicates moderate severity.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to a patched version of open5GS that includes fixed PFCP transaction handling logic (e.g., the commit referenced in public repositories).
  • Configure PFCP rate‑limiting or firewall rules to block excessive traffic to the SMF/UPF from untrusted sources, preventing resource exhaustion.
  • Monitor process health and automatically restart SMF/UPF when a SIGABRT occurs, or deploy redundancy or clustering to reduce service disruption.

Generated by OpenCVE AI on November 17, 2026 at 18:31 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Title Denial of Service in open5GS PFCP Transaction Handling Causing SIGABRT
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}

Type Values Removed Values Added
First Time appeared Open5gs
Open5gs open5gs
Vendors & Products Open5gs
Open5gs open5gs
Type Values Removed Values Added
Title Denial of Service in open5GS PFCP Transaction Handling Causing SIGABRT
Weaknesses CWE-400
Type Values Removed Values Added
Description 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.
References
Weaknesses
  • CWE-400

    Uncontrolled Resource Consumption

Sources

Status
PUBLISHED
Assigner
mitre
Published
Updated
Nov 17, 2026, 3:15 PM
Reserved
Oct 7, 2026, 12:00 AM
Status
Deferred
Published
Nov 2, 2026, 5:17 PM
Modified
Nov 17, 2026, 4:17 PM