CVE-2025-5501VulnerabilityPublished 3 Jun 2025

CVE-2025-5501: Open5GS · Reachable Assertion

Affects Open5GSSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

6.9Medium

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

EPSS: 0.7% chance of exploitation in 30 days – higher than 54% 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

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

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.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Jun 2025
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-26.

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
GitHubopen5gs/open5gs`pkg:github/open5gs/open5gs`Other threats	Affected =2.7.0 =2.7.1 =2.7.2 =2.7.3	Fixed in–

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

AI-suggested

1. Immediate application of the official patch identified by commit 2daa44adab762c47a8cef69cc984946973a845b3 to all Open5GS deployments running affected versions (2.7.0 to 2.7.3). 2. Implement network-level filtering to restrict and monitor NGAP traffic, allowing only trusted and authenticated sources to communicate with the 5G core network components. 3. Deploy intrusion detection/prevention systems (IDS/IPS) with signatures or heuristics to detect anomalous or malformed NGAP PathSwitchRequest messages indicative of exploitation attempts. 4. Conduct thorough testing of patched systems in staging environments to ensure stability and compatibility before production deployment. 5. Maintain up-to-date asset inventories to identify all Open5GS instances and ensure comprehensive patch coverage. 6. Establish monitoring and alerting for unexpected service interruptions or crashes in the SMF (Session Management Function) components handling NGAP messages. 7. Engage with vendors and community forums for ongoing updates and best practices related to Open5GS security. 8. Consider network segmentation and zero-trust principles to limit exposure of core network functions to untrusted networks.

Description

A vulnerability classified as problematic was found in Open5GS up to 2.7.3. Affected by this vulnerability is the function ngap_handle_path_switch_request_transfer of the file src/smf/ngap-handler.c of the component NGAP PathSwitchRequest Message Handler. The manipulation leads to reachable assertion. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The patch is named 2daa44adab762c47a8cef69cc984946973a845b3. It is recommended to apply a patch to fix this issue.

Impact

For European organizations, especially telecommunications providers and infrastructure operators deploying Open5GS, this vulnerability poses a risk of service disruption. The NGAP PathSwitchRequest message is essential for handling mobility and session continuity in 5G networks; thus, exploitation could lead to denial of service conditions affecting user connectivity and network reliability. This could degrade customer experience, cause financial losses, and impact critical communications services. Additionally, organizations relying on Open5GS for private 5G networks in industrial, governmental, or research contexts may face operational interruptions. While the vulnerability does not directly compromise data confidentiality or integrity, the availability impact on 5G core network functions could have cascading effects on dependent services and applications. Given the remote and unauthenticated nature of the exploit, attackers could target vulnerable systems from outside the network perimeter, increasing the threat surface. The public disclosure of the exploit details further elevates the urgency for European entities to assess and remediate affected systems to maintain network stability and service continuity.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Jul 2025, 07:03 UTC

Technical details

References

Community reviews

Related threats