CVE-2025-15176: Reachable Assertion in Open5GS
A flaw has been found in Open5GS up to 2.7.5. This affects the function decode_ipv6_header/ogs_pfcp_pdr_rule_find_by_packet of the file lib/pfcp/rule-match.c of the component PFCP Session Establishment Request Handler. Executing a manipulation can lead to reachable assertion. It is possible to launch the attack remotely. The exploit has been published and may be used. This patch is called b72d8349980076e2c033c8324f07747a86eea4f8. Applying a patch is advised to resolve this issue.
AI Analysis
Technical Summary
CVE-2025-15176 is a vulnerability identified in Open5GS, an open-source 5G core network implementation widely used for mobile network infrastructure. The flaw resides in the PFCP (Packet Forwarding Control Protocol) Session Establishment Request Handler, specifically in the functions decode_ipv6_header and ogs_pfcp_pdr_rule_find_by_packet within the source file lib/pfcp/rule-match.c. These functions are responsible for processing IPv6 headers and matching PFCP PDR (Packet Detection Rules) rules against incoming packets. Due to improper handling of crafted packets, an attacker can trigger a reachable assertion, which is a type of programmatic check that, when failed, causes the application to abort or crash. This leads to a denial of service condition by crashing the Open5GS PFCP handler. The vulnerability can be exploited remotely over the network without requiring any authentication or user interaction, making it accessible to unauthenticated attackers. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), and low impact on availability (VA:L) with no impact on confidentiality or integrity. Although no confirmed exploits in the wild have been reported, a public exploit has been published, increasing the risk of exploitation. The patch identified by commit b72d8349980076e2c033c8324f07747a86eea4f8 addresses this issue and should be applied promptly. This vulnerability affects Open5GS versions 2.7.0 through 2.7.5, which are commonly deployed in 5G core networks, particularly in research, testing, and some production environments that rely on open-source 5G core implementations.
Potential Impact
The primary impact of CVE-2025-15176 is denial of service against Open5GS 5G core network components handling PFCP session establishment. Successful exploitation can cause the PFCP handler to crash, disrupting the control plane communications between the control and user plane functions in the 5G core. This disruption can lead to dropped sessions, degraded network performance, and potential outages for mobile subscribers relying on affected infrastructure. Given the critical role of Open5GS in 5G core networks, such outages can affect telecommunication service providers, enterprises deploying private 5G networks, and research institutions. The vulnerability does not directly compromise confidentiality or integrity but can degrade availability, impacting end-user connectivity and service reliability. The ease of remote exploitation without authentication increases the risk, especially in environments where Open5GS is exposed to untrusted networks. The availability of a public exploit further raises the likelihood of attacks, potentially leading to targeted denial of service campaigns against vulnerable 5G networks.
Mitigation Recommendations
To mitigate CVE-2025-15176, organizations should immediately apply the official patch identified by commit b72d8349980076e2c033c8324f07747a86eea4f8 to all affected Open5GS instances running versions 2.7.0 through 2.7.5. Network administrators should restrict access to PFCP ports (typically UDP 8805) using firewall rules to limit exposure to trusted network segments only. Implement network segmentation to isolate 5G core components from untrusted networks and monitor PFCP traffic for anomalies or malformed packets indicative of exploitation attempts. Employ intrusion detection/prevention systems (IDS/IPS) with signatures or heuristics targeting malformed PFCP session establishment requests. Regularly update Open5GS to newer versions beyond 2.7.5 where this vulnerability is fixed. Additionally, conduct thorough testing in staging environments before deploying patches to production to avoid service disruptions. Maintain incident response plans to quickly address potential denial of service incidents affecting 5G core infrastructure.
Affected Countries
United States, China, South Korea, Japan, Germany, France, United Kingdom, India, Brazil, Australia, Canada, Italy, Spain
CVE-2025-15176: Reachable Assertion in Open5GS
Description
A flaw has been found in Open5GS up to 2.7.5. This affects the function decode_ipv6_header/ogs_pfcp_pdr_rule_find_by_packet of the file lib/pfcp/rule-match.c of the component PFCP Session Establishment Request Handler. Executing a manipulation can lead to reachable assertion. It is possible to launch the attack remotely. The exploit has been published and may be used. This patch is called b72d8349980076e2c033c8324f07747a86eea4f8. Applying a patch is advised to resolve this issue.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2025-15176 is a vulnerability identified in Open5GS, an open-source 5G core network implementation widely used for mobile network infrastructure. The flaw resides in the PFCP (Packet Forwarding Control Protocol) Session Establishment Request Handler, specifically in the functions decode_ipv6_header and ogs_pfcp_pdr_rule_find_by_packet within the source file lib/pfcp/rule-match.c. These functions are responsible for processing IPv6 headers and matching PFCP PDR (Packet Detection Rules) rules against incoming packets. Due to improper handling of crafted packets, an attacker can trigger a reachable assertion, which is a type of programmatic check that, when failed, causes the application to abort or crash. This leads to a denial of service condition by crashing the Open5GS PFCP handler. The vulnerability can be exploited remotely over the network without requiring any authentication or user interaction, making it accessible to unauthenticated attackers. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), and low impact on availability (VA:L) with no impact on confidentiality or integrity. Although no confirmed exploits in the wild have been reported, a public exploit has been published, increasing the risk of exploitation. The patch identified by commit b72d8349980076e2c033c8324f07747a86eea4f8 addresses this issue and should be applied promptly. This vulnerability affects Open5GS versions 2.7.0 through 2.7.5, which are commonly deployed in 5G core networks, particularly in research, testing, and some production environments that rely on open-source 5G core implementations.
Potential Impact
The primary impact of CVE-2025-15176 is denial of service against Open5GS 5G core network components handling PFCP session establishment. Successful exploitation can cause the PFCP handler to crash, disrupting the control plane communications between the control and user plane functions in the 5G core. This disruption can lead to dropped sessions, degraded network performance, and potential outages for mobile subscribers relying on affected infrastructure. Given the critical role of Open5GS in 5G core networks, such outages can affect telecommunication service providers, enterprises deploying private 5G networks, and research institutions. The vulnerability does not directly compromise confidentiality or integrity but can degrade availability, impacting end-user connectivity and service reliability. The ease of remote exploitation without authentication increases the risk, especially in environments where Open5GS is exposed to untrusted networks. The availability of a public exploit further raises the likelihood of attacks, potentially leading to targeted denial of service campaigns against vulnerable 5G networks.
Mitigation Recommendations
To mitigate CVE-2025-15176, organizations should immediately apply the official patch identified by commit b72d8349980076e2c033c8324f07747a86eea4f8 to all affected Open5GS instances running versions 2.7.0 through 2.7.5. Network administrators should restrict access to PFCP ports (typically UDP 8805) using firewall rules to limit exposure to trusted network segments only. Implement network segmentation to isolate 5G core components from untrusted networks and monitor PFCP traffic for anomalies or malformed packets indicative of exploitation attempts. Employ intrusion detection/prevention systems (IDS/IPS) with signatures or heuristics targeting malformed PFCP session establishment requests. Regularly update Open5GS to newer versions beyond 2.7.5 where this vulnerability is fixed. Additionally, conduct thorough testing in staging environments before deploying patches to production to avoid service disruptions. Maintain incident response plans to quickly address potential denial of service incidents affecting 5G core infrastructure.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulDB
- Date Reserved
- 2025-12-28T08:25:27.283Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 695450bddb813ff03e2bf8b7
Added to database: 12/30/2025, 10:22:53 PM
Last enriched: 2/24/2026, 10:35:18 PM
Last updated: 3/25/2026, 4:43:17 PM
Views: 66
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.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.