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-2025-15419: Denial of Service in Open5GS

0
Medium
VulnerabilityCVE-2025-15419cvecve-2025-15419
Published: Fri Jan 02 2026 (01/02/2026, 00:02:08 UTC)
Source: CVE Database V5
Product: Open5GS

Description

A weakness has been identified in Open5GS up to 2.7.6. Affected by this issue is the function sgwc_s5c_handle_create_session_response of the file src/sgwc/s5c-handler.c of the component GTPv2-C Flow Handler. Executing a manipulation can lead to denial of service. The attack needs to be launched locally. The exploit has been made available to the public and could be used for attacks. This patch is called 5aaa09907e7b9e0a326265a5f08d56f54280b5f2. It is advisable to implement a patch to correct this issue.

AI-Powered Analysis

AILast updated: 01/09/2026, 11:06:18 UTC

Technical Analysis

CVE-2025-15419 identifies a denial of service (DoS) vulnerability in Open5GS, an open-source 5G core network software widely used for implementing 5G core network functions. The vulnerability resides in the sgwc_s5c_handle_create_session_response function within the GTPv2-C Flow Handler component, specifically in the file src/sgwc/s5c-handler.c. This function handles the Create Session Response message in the S5-C interface, which is critical for session management between the Serving Gateway Control Plane (SGWC) and the Packet Gateway Control Plane (PGWC). The flaw allows a local attacker with limited privileges to manipulate the function’s processing logic, causing the software to crash or become unresponsive, resulting in a denial of service. The attack requires local access to the system running Open5GS, meaning remote exploitation is not feasible without prior access. No user interaction or elevated privileges beyond low-level local access are needed, and the vulnerability does not affect confidentiality or integrity but impacts availability. The CVSS v4.0 score is 4.8 (medium), reflecting the limited attack vector (local) but significant impact on service availability. The vulnerability affects Open5GS versions 2.7.0 through 2.7.6. A patch identified by commit 5aaa09907e7b9e0a326265a5f08d56f54280b5f2 has been released to remediate the issue. While no known exploits have been observed in the wild, the exploit code is publicly available, increasing the risk of exploitation by insiders or attackers with local access. Given Open5GS’s role in 5G core networks, successful exploitation could disrupt mobile network services, impacting subscribers and network operators.

Potential Impact

For European organizations deploying Open5GS as part of their 5G core network infrastructure, this vulnerability poses a risk of service disruption through denial of service attacks. The affected component is critical for session management in the 5G core, so exploitation could lead to dropped sessions, degraded network performance, or complete unavailability of core network functions. This can impact mobile network operators, enterprises running private 5G networks, and service providers relying on Open5GS for connectivity. The disruption could affect end users’ mobile services, including voice, data, and IoT communications. Since the attack requires local access, the threat is higher in environments where internal network segmentation or host security is weak, or where insider threats exist. The availability impact could lead to financial losses, reputational damage, and regulatory scrutiny under EU telecom and data protection regulations. Additionally, the public availability of exploit code increases the urgency for mitigation. Organizations with critical infrastructure or those providing essential communications services are particularly vulnerable to operational disruptions caused by this flaw.

Mitigation Recommendations

To mitigate this vulnerability, European organizations should promptly apply the official patch released for Open5GS that addresses CVE-2025-15419. In addition to patching, organizations should enforce strict access controls to limit local access to systems running Open5GS, including hardened host configurations and role-based access controls. Network segmentation should be implemented to isolate core network components from less trusted internal networks and users. Continuous monitoring and logging of Open5GS processes and system behavior can help detect anomalous activity indicative of exploitation attempts. Employing host-based intrusion detection systems (HIDS) and endpoint protection solutions can further reduce risk. Regular security audits and vulnerability assessments of 5G core infrastructure should be conducted to identify and remediate weaknesses. Finally, organizations should develop and test incident response plans specific to 5G core network disruptions to minimize downtime in case of exploitation.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2026-01-01T10:57:11.786Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 695714c3db813ff03e909831

Added to database: 1/2/2026, 12:43:47 AM

Last enriched: 1/9/2026, 11:06:18 AM

Last updated: 2/6/2026, 6:46:59 PM

Views: 56

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