CVE-2026-2517VulnerabilityPublished 15 Feb 2026Updated 23 Feb 2026

CVE-2026-2517: Open5GS · Denial of Service

Affects Open5GSSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

6.9Medium

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

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

CVSS:4.0/AV:N/AC:L/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: Low
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: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
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 15 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

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 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
Open5GS	Affected =2.7.0 =2.7.1 =2.7.2 =2.7.3 =2.7.4 =2.7.5 =2.7.6	Fixed in–

CPE configurations (1)

cpe:2.3:a:open5gs:open5gs:*:*:*:*:*:*:*:*

AI-suggested

To mitigate CVE-2026-2517, organizations should first monitor Open5GS SMF logs and network traffic for anomalous or malformed GTPv2 packets targeting the ogs_gtp2_parse_tft function. Implement network-level filtering or rate limiting on GTPv2 control plane traffic to reduce exposure to malformed packets. Deploy intrusion detection/prevention systems (IDS/IPS) with updated signatures to detect attempts exploiting this vulnerability. If possible, isolate the SMF component within a protected network segment to limit attack surface. Engage with the Open5GS community or maintainers to track patch releases and apply updates promptly once available. As a temporary workaround, consider disabling or restricting features that process TFT (Traffic Flow Template) parameters if feasible. Conduct regular backups and prepare incident response plans to quickly recover from potential DoS events. Finally, evaluate alternative 5G core solutions or vendor support if timely patches are not forthcoming.

Description

A security flaw has been discovered in Open5GS up to 2.7.6. This vulnerability affects the function ogs_gtp2_parse_tft in the library lib/gtp/v2/types.c of the component SMF. Performing a manipulation of the argument pf[0].content.length results in denial of service. The attack is possible to be carried out remotely. The exploit has been released to the public and may be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.

Impact

The primary impact of CVE-2026-2517 is denial of service against the SMF component of Open5GS, which can lead to service outages or degradation in 5G core network operations. This can disrupt session management, affecting user connectivity, data sessions, and overall network reliability. For telecom operators and service providers relying on Open5GS, this could translate into customer service interruptions, loss of revenue, and reputational damage. In critical infrastructure contexts, such as emergency services or industrial IoT relying on 5G, the disruption could have broader societal impacts. Since the vulnerability can be exploited remotely without authentication, attackers can launch DoS attacks at scale or as part of coordinated campaigns. The lack of an official patch increases exposure time, and the public availability of exploits raises the risk of opportunistic attacks. Organizations using Open5GS in production environments are particularly vulnerable, especially those with limited network segmentation or insufficient monitoring of control plane traffic.

Summary

CVE-2026-2517 is a denial of service vulnerability identified in Open5GS, an open-source 5G core network implementation, affecting versions 2.7.0 through 2.7.6. The vulnerability exists in the SMF (Session Management Function) component, specifically within the ogs_gtp2_parse_tft function located in the lib/gtp/v2/types.c source file. The root cause is improper validation or handling of the pf[0].content.length parameter, which can be manipulated by a remote attacker to trigger a denial of service condition. This manipulation likely leads to memory corruption, crashes, or infinite loops causing the SMF process to become unresponsive or terminate unexpectedly. The attack vector is network-based, requiring no authentication or user interaction, making it straightforward for remote exploitation. The SMF is a critical element in 5G core networks responsible for session management and policy enforcement, so disruption here can affect the overall network service availability. Public exploit code has been made available, increasing the urgency for mitigation. The CVSS v4.0 base score is 6.9 (medium severity), reflecting the ease of exploitation and impact limited to availability without confidentiality or integrity compromise.

References

Community reviews

Loading reviews…