VulnerabilityPublished 19 Dec 2025Updated 24 Feb 2026

CVE-2025-14954: Open5GS · Reachable Assertion

Affects Open5GSSource CVE Database V5

Public exploit available · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score

6.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: High
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubopen5gs/open5gs`pkg:github/open5gs/open5gs`Other threats	Affected 2.7.0 – 2.7.6 7 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations running Open5GS versions 2.7.0 through 2.7.6 should prioritize applying the official patch identified by commit 442369dcd964f03d95429a6a01a57ed21f7779b7 to remediate this vulnerability. Network operators should also implement strict filtering and validation of PFCP traffic at network boundaries to limit exposure to potentially malicious packets. Deploying monitoring and anomaly detection focused on PFCP message patterns can help identify exploitation attempts. Segmentation of 5G core network components and limiting access to PFCP interfaces to trusted management networks reduces the attack surface. Regularly updating Open5GS and other 5G core components to the latest stable versions is critical. Additionally, conducting security audits and penetration testing on 5G core implementations can uncover similar logic flaws before exploitation. Operators should maintain incident response plans tailored to 5G network disruptions.

Description

A vulnerability has been found in Open5GS up to 2.7.6. Affected is the function ogs_pfcp_pdr_find_or_add/ogs_pfcp_far_find_or_add/ogs_pfcp_urr_find_or_add/ogs_pfcp_qer_find_or_add in the library lib/pfcp/context.c of the component QER/FAR/URR/PDR. The manipulation leads to reachable assertion. It is possible to initiate the attack remotely. The attack's complexity is rated as high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. The identifier of the patch is 442369dcd964f03d95429a6a01a57ed21f7779b7. Applying a patch is the recommended action to fix this issue.

Impact

The primary impact of this vulnerability is denial of service due to assertion failures causing Open5GS components to crash or restart. This can disrupt 5G core network functions such as session management, QoS enforcement, and usage reporting, potentially degrading network reliability and availability. For telecom operators and service providers relying on Open5GS, this could lead to service interruptions affecting end-users, impacting voice, data, and signaling services. While the vulnerability does not appear to allow remote code execution or data compromise, the loss of availability in critical 5G infrastructure components can have significant operational and financial consequences. The high complexity of exploitation reduces the likelihood of widespread attacks but does not eliminate risk, especially from well-resourced adversaries targeting telecom infrastructure. The vulnerability's presence in multiple PFCP-related functions increases the attack surface within the 5G control plane.

Summary

CVE-2025-14954 is a vulnerability identified in Open5GS, an open-source 5G core network implementation, specifically in versions 2.7.0 through 2.7.6. The issue resides in the PFCP (Packet Forwarding Control Protocol) context management functions: ogs_pfcp_pdr_find_or_add, ogs_pfcp_far_find_or_add, ogs_pfcp_urr_find_or_add, and ogs_pfcp_qer_find_or_add within the lib/pfcp/context.c source file. These functions handle the creation or retrieval of PFCP entities such as PDR (Packet Detection Rule), FAR (Forwarding Action Rule), URR (Usage Reporting Rule), and QER (QoS Enforcement Rule). The vulnerability manifests as a reachable assertion failure, which can be triggered remotely by an attacker sending crafted PFCP messages. This assertion failure can cause the Open5GS process to terminate unexpectedly, resulting in denial of service conditions. The attack does not require authentication or user interaction but has a high complexity rating, indicating that successful exploitation demands deep protocol knowledge and precise message crafting. The vulnerability was publicly disclosed on December 19, 2025, with a patch identified by commit 442369dcd964f03d95429a6a01a57ed21f7779b7 recommended to remediate the issue. The CVSS 4.0 vector (AV:N/AC:H/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P) reflects a network attack vector with high complexity, no privileges or user interaction required, and limited impact on availability. No known exploits have been observed in the wild to date.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Feb 2026, 23:06 UTC

Technical details

References

Community reviews

Related threats