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-2521: Memory Corruption in Open5GS

0
Medium
VulnerabilityCVE-2026-2521cvecve-2026-2521
Published: Sun Feb 15 2026 (02/15/2026, 23:02:07 UTC)
Source: CVE Database V5
Product: Open5GS

Description

A weakness has been identified in Open5GS up to 2.7.6. This issue affects the function sgwc_s5c_handle_create_session_response of the component SGW-C. Executing a manipulation can lead to memory corruption. The attack may be performed from remote. The exploit has been made available to the public and could be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.

AI-Powered Analysis

AILast updated: 02/15/2026, 23:18:59 UTC

Technical Analysis

CVE-2026-2521 identifies a memory corruption vulnerability in the Open5GS project, an open-source implementation of 5G core network components. The issue resides in the SGW-C (Serving Gateway Control plane) component, specifically within the function sgwc_s5c_handle_create_session_response. This function handles session creation responses over the S5-C interface, which is critical for managing user sessions in the 5G core network. The vulnerability allows an attacker to remotely manipulate inputs to this function, causing memory corruption that could lead to denial of service or potentially arbitrary code execution, depending on the exploitation specifics. The attack vector is network-based, requiring no authentication or user interaction, increasing the risk profile. The vulnerability affects all Open5GS versions from 2.7.0 through 2.7.6. Although the Open5GS project was notified early, no patch or official response has been released at the time of publication. The CVSS 4.0 score is 6.9 (medium severity), reflecting the ease of remote exploitation but limited impact scope and no known exploits in the wild. Open5GS is increasingly used by telecom operators and enterprises for private and public 5G core deployments due to its open-source nature and flexibility. This vulnerability thus poses a risk to the integrity and availability of 5G core network functions, potentially disrupting mobile services or enabling further attacks within the network infrastructure.

Potential Impact

For European organizations, the impact of CVE-2026-2521 can be significant, especially for telecom operators and enterprises deploying Open5GS-based 5G core networks. Exploitation could lead to memory corruption in the SGW-C component, resulting in service disruptions such as dropped sessions, degraded network performance, or denial of service. This can affect end-user connectivity and critical services relying on 5G networks, including IoT, industrial automation, and emergency communications. Additionally, if exploited for arbitrary code execution, attackers could gain control over core network functions, leading to data breaches, traffic interception, or further lateral movement within the network. The lack of authentication and user interaction requirements lowers the barrier for attackers, increasing the threat level. Given the strategic importance of 5G infrastructure in Europe’s digital economy and critical services, this vulnerability could have cascading effects on national security and economic activities. Organizations using Open5GS must consider the risk of targeted attacks by advanced threat actors seeking to disrupt or surveil 5G communications.

Mitigation Recommendations

1. Monitor the Open5GS project and related security advisories closely for official patches or updates addressing CVE-2026-2521 and apply them immediately upon release. 2. Until patches are available, implement network-level protections such as firewall rules and intrusion detection/prevention systems (IDS/IPS) to restrict and monitor traffic to the SGW-C interfaces, particularly the S5-C interface. 3. Employ strict network segmentation to isolate 5G core network components from other enterprise or public networks, minimizing exposure to external attackers. 4. Conduct regular security assessments and fuzz testing on Open5GS deployments to detect anomalous behavior or potential exploitation attempts. 5. Enhance logging and monitoring of SGW-C component activities to identify suspicious session creation responses or memory anomalies. 6. Limit access to management interfaces and ensure strong authentication and authorization controls are in place. 7. Engage with telecom vendors and open-source communities to share threat intelligence and coordinate response efforts. 8. Prepare incident response plans specific to 5G core network compromises, including rapid containment and recovery procedures.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2026-02-15T08:36:09.388Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 699253b94b0e3abdf99ab24e

Added to database: 2/15/2026, 11:16:09 PM

Last enriched: 2/15/2026, 11:18:59 PM

Last updated: 2/20/2026, 11:18:07 PM

Views: 43

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