Skip to main content
CVE-2025-6952VulnerabilityPublished

CVE-2025-6952: Open5GS · Reachable Assertion

Affects Open5GSSource CVE Database V5

0

Not known to be exploited · CVSS 4.8 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Affected software

ProductAffectedFixed in
GitHubopen5gs/open5gspkg:github/open5gs/open5gsOther threatsAffected
  • =2.7.0
  • =2.7.1
  • =2.7.2
  • =2.7.3
  • =2.7.4
  • =2.7.5
Fixed in–

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

AI-suggested

European organizations should immediately verify if their Open5GS deployments are running affected versions (2.7.0 to 2.7.5) and apply the official patch identified by commit 53e9e059ed96b940f7ddcd9a2b68cb512524d5db. Beyond patching, it is crucial to restrict and monitor local access to Open5GS hosts, implementing strict access controls and auditing to detect unauthorized local activity. Employing host-based intrusion detection systems (HIDS) can help identify attempts to exploit this vulnerability. Network segmentation should be enforced to isolate 5G core components from less trusted network zones, minimizing the risk of lateral movement. Additionally, organizations should conduct regular security assessments and penetration tests focusing on local privilege escalation and assertion failure scenarios. Maintaining up-to-date backups and failover mechanisms for the AMF service can reduce downtime in case of exploitation. Finally, integrating vulnerability management processes that include monitoring for new Open5GS vulnerabilities and timely patch deployment is essential to maintain a secure 5G core environment.

Description

A vulnerability, which was classified as problematic, has been found in Open5GS up to 2.7.5. This issue affects the function amf_state_operational of the file src/amf/amf-sm.c of the component AMF Service. The manipulation leads to reachable assertion. It is possible to launch the attack on the local host. The identifier of the patch is 53e9e059ed96b940f7ddcd9a2b68cb512524d5db. It is recommended to apply a patch to fix this issue.

References

Community reviews

Loading reviews…