Skip to main content
VulnerabilityPublished

CVE-2025-52288: Open5GS thru · Uncontrolled Resource Consumption

Source CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Sep 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 26 Oct 2026.

What to do

AI-suggested

To mitigate this vulnerability, European organizations should first monitor Open5GS project communications and security advisories for official patches or updates addressing CVE-2025-52288. Until a patch is available, operators should implement strict network segmentation and access controls to limit exposure of the AMF component to untrusted or external networks, reducing the risk of malicious UE message injection. Deploying anomaly detection systems to monitor unusual UE connect/disconnect message patterns can help identify attempted exploitation attempts early. Network operators should also consider rate limiting or filtering UE signaling messages to prevent repeated rapid connect/disconnect sequences that could trigger the assertion failure. Conducting thorough testing in controlled environments to reproduce the issue and validate mitigations is advisable. Additionally, organizations should review their incident response plans to prepare for potential DoS events affecting 5G core components. Collaboration with vendors and the open-source community to expedite patch development and deployment is critical. Finally, maintaining up-to-date backups and redundancy for core network functions can help ensure service continuity in case of an attack.

Description

Assertion failure in function ngap_build_downlink_nas_transport in file src/amf/ngap-build.c, the Access and Mobility Management Function (AMF) component, in Open5GS thru 2.7.5 allowing attackers to cause a denial of service or other unspecified impacts via repeated UE connect and disconnect message sequences.

References

Community reviews

Loading reviews…