VulnerabilityPublished 17 Jan 2026Updated 23 Feb 2026

CVE-2025-15531: Open5GS · Reachable Assertion

Affects Open5GSSource CVE Database V5

Public exploit available · CVSS 6.9 Medium · fixed in 2.7.5 : patch Open5GS as a priority.

Data as of 26 Oct 2026, 17:16 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 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.7.5

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 17 Jan 2026
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
Open5GS	Affected 2.7.0 – 2.7.5 6 affected builds	Fixed in–
GitHubopen5gs/open5gs`pkg:github/open5gs/open5gs`Other threats	Affected 2.7.0 – 2.7.5 6 affected builds	Fixed in–

CPE configurations (1)

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

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

AI-suggested

To mitigate CVE-2025-15531, organizations should immediately upgrade Open5GS to the latest version beyond 2.7.5 where the vulnerability is fixed. If immediate upgrade is not feasible, network administrators should restrict access to the affected sgwc service using network segmentation and firewall rules to limit exposure to trusted management networks only. Implementing strict ingress filtering and monitoring for anomalous bearer addition requests can help detect exploitation attempts. Additionally, deploying runtime monitoring and automated process recovery can reduce downtime caused by crashes. Regularly auditing Open5GS configurations and applying security patches promptly is critical. Telecom operators should also consider deploying redundancy and failover mechanisms in their 5G core infrastructure to minimize service impact from potential DoS events. Finally, maintaining awareness of public exploit releases and threat intelligence feeds will help in proactive defense.

Description

A vulnerability was identified in Open5GS up to 2.7.5. This vulnerability affects the function sgwc_bearer_add of the file src/sgwc/context.c. The manipulation leads to reachable assertion. The attack is possible to be carried out remotely. The exploit is publicly available and might be used. The issue report is flagged as already-fixed.

Impact

The primary impact of CVE-2025-15531 is a denial of service against Open5GS deployments, which can disrupt 5G core network operations. A successful exploit causes the sgwc process to crash due to assertion failure, potentially leading to service outages or degraded network performance. This can affect mobile network operators relying on Open5GS for session management and bearer control, impacting end-user connectivity and service availability. In large-scale deployments, repeated exploitation could cause significant network instability and operational challenges. While the vulnerability does not compromise data confidentiality or integrity, the availability impact on critical telecom infrastructure can have cascading effects on emergency services, enterprise communications, and consumer mobile services. The ease of remote exploitation without authentication increases the risk profile, especially in environments where Open5GS is exposed to untrusted networks. Organizations that do not promptly patch may face increased risk of service disruption and potential reputational damage.

References

Community reviews

Loading reviews…