Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-1736: Reachable Assertion in Open5GS

0
Medium
VulnerabilityCVE-2026-1736cvecve-2026-1736
Published: Mon Feb 02 2026 (02/02/2026, 00:32:06 UTC)
Source: CVE Database V5
Product: Open5GS

Description

A security vulnerability has been detected in Open5GS up to 2.7.6. Impacted is the function sgwc_s11_handle_create_indirect_data_forwarding_tunnel_request of the file /src/sgwc/s11-handler.c of the component SGWC. Such manipulation leads to reachable assertion. The attack may be launched remotely. The exploit has been disclosed publicly and may be used. A patch should be applied to remediate this issue. The issue report is flagged as already-fixed.

AI-Powered Analysis

AILast updated: 02/02/2026, 01:12:08 UTC

Technical Analysis

CVE-2026-1736 is a security vulnerability identified in Open5GS, an open-source 5G core network implementation widely used for research and production environments. The flaw exists in the SGWC (Serving Gateway Control) component, specifically within the function sgwc_s11_handle_create_indirect_data_forwarding_tunnel_request located in /src/sgwc/s11-handler.c. This function handles Create Indirect Data Forwarding Tunnel requests over the S11 interface, which is critical for managing user plane tunnels between the Serving Gateway and other 5G core components. The vulnerability manifests as a reachable assertion failure, meaning that crafted network messages can trigger an assertion condition that causes the process to terminate unexpectedly. Since the attack vector is network-exposed and requires no authentication or user interaction, an attacker can remotely cause a denial of service by crashing the SGWC process, potentially disrupting 5G data forwarding services. The CVSS v4.0 base score is 6.9 (medium severity), reflecting the network attack vector, low complexity, and no privileges or user interaction required, but limited impact confined to availability. The vulnerability was publicly disclosed and fixed after version 2.7.6, and no known exploits have been observed in the wild to date. The issue underscores the importance of robust input validation and error handling in telecom protocol implementations to maintain service continuity in 5G networks.

Potential Impact

For European organizations, particularly telecom operators and infrastructure providers deploying Open5GS as part of their 5G core network, this vulnerability poses a risk of service disruption. An attacker exploiting this flaw can remotely crash the SGWC component, leading to denial of service conditions affecting user plane data forwarding. This could degrade network performance, interrupt subscriber connectivity, and impact critical services relying on 5G connectivity. Given the increasing reliance on 5G for industrial automation, smart city applications, and emergency services in Europe, such disruptions could have broader economic and societal consequences. Additionally, repeated exploitation attempts could increase operational costs due to incident response and recovery efforts. While the vulnerability does not directly compromise confidentiality or integrity, availability impacts in telecom infrastructure are critical and can cascade to affect multiple dependent services and customers.

Mitigation Recommendations

European organizations should immediately apply the official patch or upgrade Open5GS to a version later than 2.7.6 where the vulnerability is fixed. In parallel, network segmentation and strict access controls should be enforced on the S11 interface to limit exposure to untrusted networks. Deploying intrusion detection or anomaly detection systems that monitor S11 signaling traffic can help identify suspicious or malformed tunnel creation requests indicative of exploitation attempts. Operators should also implement robust logging and alerting for SGWC process crashes or restarts to enable rapid incident response. Regular security audits and fuzz testing of telecom protocol handlers are recommended to proactively identify similar vulnerabilities. Finally, organizations should maintain up-to-date threat intelligence feeds and collaborate with industry groups to share information about emerging threats targeting 5G core components.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2026-02-01T07:44:34.393Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 697ff68cac06320222673ab0

Added to database: 2/2/2026, 12:57:48 AM

Last enriched: 2/2/2026, 1:12:08 AM

Last updated: 2/7/2026, 1:40:02 AM

Views: 39

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats