CVE-2025-15539: Denial of Service in Open5GS
CVE-2025-15539 is a medium severity denial of service (DoS) vulnerability in Open5GS versions up to 2. 7. 6. It affects the sgwc_s11_handle_downlink_data_notification_ack function in the sgwc component, allowing remote attackers to cause a DoS without authentication or user interaction. The vulnerability has a CVSS 4. 0 score of 6. 9 and has been publicly disclosed, though no known exploits are currently active in the wild. A patch is available and recommended to mitigate the issue. This vulnerability could disrupt 5G core network operations relying on Open5GS, impacting service availability. European telecom operators and infrastructure providers using Open5GS should prioritize patching to maintain network stability and avoid service outages.
AI Analysis
Technical Summary
CVE-2025-15539 is a denial of service vulnerability identified in Open5GS, an open-source 5G core network implementation widely used for 5G mobile network infrastructure. The flaw exists in the sgwc_s11_handle_downlink_data_notification_ack function within the sgwc component, specifically in the file src/sgwc/s11-handler.c. This function handles downlink data notification acknowledgments on the S11 interface, which is critical for communication between the Serving Gateway Control plane (SGWC) and the Mobility Management Entity (MME) or Access and Mobility Management Function (AMF) in 5G networks. Due to improper handling of certain inputs, an attacker can remotely trigger a denial of service condition, causing the affected component to crash or become unresponsive, thereby disrupting the 5G core network's ability to process downlink data notifications. The vulnerability requires no authentication or user interaction, increasing its risk profile. The CVSS 4.0 score of 6.9 reflects a medium severity, with a network attack vector, low attack complexity, and no privileges or user interaction required. The issue has been publicly disclosed, and a patch has been issued (commit b4707272c1caf6a7d4dca905694ea55557a0545f) to fix the vulnerability. While no known exploits are currently observed in the wild, the public disclosure means attackers could develop exploits, making timely patching critical. This vulnerability primarily impacts organizations deploying Open5GS for 5G core network functions, potentially causing service outages and impacting network reliability.
Potential Impact
For European organizations, particularly telecom operators and infrastructure providers deploying Open5GS in their 5G core networks, this vulnerability poses a significant risk to network availability. A successful denial of service attack could disrupt the processing of downlink data notifications, leading to partial or complete service outages for mobile subscribers. This disruption can affect critical communications, emergency services, and enterprise connectivity relying on 5G networks. Given the increasing reliance on 5G for digital transformation, IoT, and critical infrastructure, such outages could have cascading effects on business operations and public safety. Additionally, the remote and unauthenticated nature of the vulnerability means attackers can exploit it without insider access, increasing the threat landscape. European organizations may also face reputational damage and regulatory scrutiny if service disruptions occur. The impact is magnified in countries with advanced 5G deployments and where Open5GS is used as a cost-effective or open-source core network solution.
Mitigation Recommendations
European organizations should immediately assess their 5G core network deployments to identify Open5GS versions 2.7.0 through 2.7.6 in use. The primary mitigation is to apply the official patch (commit b4707272c1caf6a7d4dca905694ea55557a0545f) provided by the Open5GS project to remediate the vulnerability. Network operators should also implement robust network segmentation and firewall rules to restrict access to the S11 interface, limiting exposure to untrusted networks. Continuous monitoring of network traffic for anomalies related to downlink data notifications can help detect attempted exploitation. Employing rate limiting and anomaly detection on the S11 interface may reduce the risk of DoS attacks. Operators should maintain up-to-date inventories of network components and ensure timely patch management processes are in place. Coordination with national cybersecurity agencies and telecom regulators can provide additional threat intelligence and support. Finally, contingency plans for rapid incident response and service restoration should be reviewed and tested.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Netherlands, Sweden, Finland, Poland, Belgium
CVE-2025-15539: Denial of Service in Open5GS
Description
CVE-2025-15539 is a medium severity denial of service (DoS) vulnerability in Open5GS versions up to 2. 7. 6. It affects the sgwc_s11_handle_downlink_data_notification_ack function in the sgwc component, allowing remote attackers to cause a DoS without authentication or user interaction. The vulnerability has a CVSS 4. 0 score of 6. 9 and has been publicly disclosed, though no known exploits are currently active in the wild. A patch is available and recommended to mitigate the issue. This vulnerability could disrupt 5G core network operations relying on Open5GS, impacting service availability. European telecom operators and infrastructure providers using Open5GS should prioritize patching to maintain network stability and avoid service outages.
AI-Powered Analysis
Technical Analysis
CVE-2025-15539 is a denial of service vulnerability identified in Open5GS, an open-source 5G core network implementation widely used for 5G mobile network infrastructure. The flaw exists in the sgwc_s11_handle_downlink_data_notification_ack function within the sgwc component, specifically in the file src/sgwc/s11-handler.c. This function handles downlink data notification acknowledgments on the S11 interface, which is critical for communication between the Serving Gateway Control plane (SGWC) and the Mobility Management Entity (MME) or Access and Mobility Management Function (AMF) in 5G networks. Due to improper handling of certain inputs, an attacker can remotely trigger a denial of service condition, causing the affected component to crash or become unresponsive, thereby disrupting the 5G core network's ability to process downlink data notifications. The vulnerability requires no authentication or user interaction, increasing its risk profile. The CVSS 4.0 score of 6.9 reflects a medium severity, with a network attack vector, low attack complexity, and no privileges or user interaction required. The issue has been publicly disclosed, and a patch has been issued (commit b4707272c1caf6a7d4dca905694ea55557a0545f) to fix the vulnerability. While no known exploits are currently observed in the wild, the public disclosure means attackers could develop exploits, making timely patching critical. This vulnerability primarily impacts organizations deploying Open5GS for 5G core network functions, potentially causing service outages and impacting network reliability.
Potential Impact
For European organizations, particularly telecom operators and infrastructure providers deploying Open5GS in their 5G core networks, this vulnerability poses a significant risk to network availability. A successful denial of service attack could disrupt the processing of downlink data notifications, leading to partial or complete service outages for mobile subscribers. This disruption can affect critical communications, emergency services, and enterprise connectivity relying on 5G networks. Given the increasing reliance on 5G for digital transformation, IoT, and critical infrastructure, such outages could have cascading effects on business operations and public safety. Additionally, the remote and unauthenticated nature of the vulnerability means attackers can exploit it without insider access, increasing the threat landscape. European organizations may also face reputational damage and regulatory scrutiny if service disruptions occur. The impact is magnified in countries with advanced 5G deployments and where Open5GS is used as a cost-effective or open-source core network solution.
Mitigation Recommendations
European organizations should immediately assess their 5G core network deployments to identify Open5GS versions 2.7.0 through 2.7.6 in use. The primary mitigation is to apply the official patch (commit b4707272c1caf6a7d4dca905694ea55557a0545f) provided by the Open5GS project to remediate the vulnerability. Network operators should also implement robust network segmentation and firewall rules to restrict access to the S11 interface, limiting exposure to untrusted networks. Continuous monitoring of network traffic for anomalies related to downlink data notifications can help detect attempted exploitation. Employing rate limiting and anomaly detection on the S11 interface may reduce the risk of DoS attacks. Operators should maintain up-to-date inventories of network components and ensure timely patch management processes are in place. Coordination with national cybersecurity agencies and telecom regulators can provide additional threat intelligence and support. Finally, contingency plans for rapid incident response and service restoration should be reviewed and tested.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulDB
- Date Reserved
- 2026-01-18T07:33:03.737Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 696d6fb9d302b072d906e96e
Added to database: 1/18/2026, 11:41:45 PM
Last enriched: 1/26/2026, 8:02:26 PM
Last updated: 2/7/2026, 5:32:58 AM
Views: 119
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-2075: Improper Access Controls in yeqifu warehouse
MediumCVE-2026-2073: SQL Injection in itsourcecode School Management System
MediumCVE-2026-25845
LowCVE-2026-25844
LowCVE-2026-25843
LowActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
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.