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

0
Medium
VulnerabilityCVE-2025-15528cvecve-2025-15528
Published: Fri Jan 16 2026 (01/16/2026, 22:02:07 UTC)
Source: CVE Database V5
Product: Open5GS

Description

A vulnerability has been found in Open5GS up to 2.7.6. Affected by this vulnerability is an unknown functionality of the component GTPv2 Bearer Response Handler. Such manipulation leads to denial of service. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The name of the patch is 98f76e98df35cd6a35e868aa62715db7f8141ac1. A patch should be applied to remediate this issue.

AI-Powered Analysis

AILast updated: 01/24/2026, 19:55:21 UTC

Technical Analysis

CVE-2025-15528 is a vulnerability in the Open5GS project, an open-source implementation of 5G core network functions widely used for mobile network infrastructure. The flaw resides in the GTPv2 Bearer Response Handler component, which processes GPRS Tunneling Protocol version 2 messages related to bearer management. Specifically, crafted GTPv2 Bearer Response messages can trigger a denial of service condition, causing the affected Open5GS node to crash or become unresponsive. The vulnerability affects all Open5GS versions from 2.7.0 through 2.7.6. Exploitation requires no authentication, privileges, or user interaction, and can be performed remotely by sending maliciously crafted packets to the vulnerable service. The CVSS v4.0 base score is 6.9, indicating a medium severity level primarily due to the impact on availability and ease of exploitation. The vulnerability does not affect confidentiality or integrity. The patch identified by commit 98f76e98df35cd6a35e868aa62715db7f8141ac1 addresses the issue by correcting the handling logic in the GTPv2 Bearer Response Handler to prevent the denial of service condition. Although no known exploits are currently observed in the wild, the public disclosure of the vulnerability increases the risk of exploitation attempts. Open5GS is used by telecom operators, research institutions, and enterprises deploying private 5G networks, making this vulnerability relevant to critical communication infrastructure. Attackers exploiting this flaw could disrupt mobile network services, impacting voice, data, and signaling availability.

Potential Impact

For European organizations, the primary impact of CVE-2025-15528 is the potential disruption of 5G core network services relying on Open5GS. This denial of service could lead to temporary unavailability of mobile connectivity, affecting enterprise communications, IoT deployments, and public safety networks that depend on stable 5G infrastructure. Telecom operators using Open5GS in their core network could experience service outages, customer dissatisfaction, and financial losses. Enterprises deploying private 5G networks for industrial automation, logistics, or smart city applications may face operational disruptions. The impact on confidentiality and integrity is minimal, but availability degradation in critical communication infrastructure can have cascading effects on dependent services. Given the remote and unauthenticated nature of the exploit, attackers can launch denial of service attacks from outside the network perimeter, increasing the threat surface. The medium severity rating reflects the balance between the ease of exploitation and the limited scope of impact to availability only. However, in sectors where continuous connectivity is essential, even temporary outages can have significant consequences.

Mitigation Recommendations

To mitigate CVE-2025-15528, European organizations should prioritize applying the official patch identified by commit 98f76e98df35cd6a35e868aa62715db7f8141ac1 to all Open5GS deployments running affected versions (2.7.0 through 2.7.6). Network operators should implement strict filtering and validation of GTPv2 traffic at network boundaries to detect and block malformed or suspicious bearer response messages. Deploying intrusion detection/prevention systems (IDS/IPS) with signatures tuned for GTP anomalies can help identify exploitation attempts. Network segmentation should isolate Open5GS core components from untrusted networks to reduce exposure. Regular monitoring and logging of GTPv2 traffic patterns can provide early warning of attack attempts. Organizations should also conduct security audits and penetration testing focused on telecom core components to identify other potential weaknesses. Maintaining up-to-date backups and incident response plans will help minimize downtime in case of successful denial of service attacks. Collaboration with telecom vendors and security communities to share threat intelligence related to Open5GS vulnerabilities is recommended. Finally, consider deploying redundant Open5GS instances or failover mechanisms to maintain service continuity during attacks.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2026-01-16T16:35:43.587Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 696ab9f0b22c7ad868fb1a90

Added to database: 1/16/2026, 10:21:36 PM

Last enriched: 1/24/2026, 7:55:21 PM

Last updated: 2/7/2026, 11:41:34 AM

Views: 28

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