Cyber Resilience

CVE-2025-5935

Open5Gs ≤ 2.7.6

Public PoC
Published
10 June 2025
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v4 5.5
Click a component to see what it means
Raw vectorCVSS: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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0078 53th percentile
Risk Priority 41 floored blend · peak EPSS

Summary

CVE-2025-5935 is a medium-severity Improper Resource Shutdown or Release (CWE-404) vulnerability in Open5Gs Open5Gs. Its CVSS base score is 5.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 47% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

A vulnerability identified as CVE-2025-5935 exists in Open5GS versions up to 2.7.3 within the AMF/MME component. Specifically, the common_register_state function in src/mme/emm-sm.c is affected by improper handling of the ran_ue_id argument, which can trigger a denial of service. The flaw is tracked under CWE-404 and carries a CVSS 4.0 score of 5.5 reflecting network-accessible impact limited to availability.

Remote attackers can exploit the issue without authentication or user interaction by sending crafted input that manipulates the ran_ue_id value, resulting in service disruption to the affected mobile core functions. Public disclosure of an exploit has occurred, although the EPSS score remains flat at 0.0115 with no material increase observed.

The project maintainers have published a patch under commit 62cb99755243c9c38e4c060c5d8d0e158fe8cdd5 that addresses the root cause. Security advisories and the associated GitHub issue recommend applying this update promptly to eliminate the denial-of-service condition.

EU & UK References

Vulnerability Data

A vulnerability was found in Open5GS up to 2.7.3. It has been declared as problematic. Affected by this vulnerability is the function common_register_state of the file src/mme/emm-sm.c of the component AMF/MME. The manipulation of the argument ran_ue_id leads to denial…

more

of service. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The identifier of the patch is 62cb99755243c9c38e4c060c5d8d0e158fe8cdd5. It is recommended to apply a patch to fix this issue.

CWE(s)
CWE-404

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
attack.mitre.org →
T1499.001 OS Exhaustion Flood Impact
Adversaries may launch a denial of service (DoS) attack targeting an endpoint's operating system (OS).
attack.mitre.org →
T1499.003 Application Exhaustion Flood Impact
Adversaries may target resource intensive features of applications to cause a denial of service (DoS), denying availability to those applications.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-1587Same product: Open5Gs Open5Gs
CVE-2025-15418Same product: Open5Gs Open5Gs
CVE-2026-8120Same product: Open5Gs Open5Gs
CVE-2024-51179Same product: Open5Gs Open5Gs
CVE-2026-8119Same product: Open5Gs Open5Gs
CVE-2026-8123Same product: Open5Gs Open5Gs
CVE-2026-8744Same product: Open5Gs Open5Gs
CVE-2026-8251Same product: Open5Gs Open5Gs
CVE-2025-1925Same product: Open5Gs Open5Gs
CVE-2026-7587Same product: Open5Gs Open5Gs

Affected Assets

open5gs
open5gs
≤ 2.7.6

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover missing or incorrect resource releases after code is written.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles can require explicit resource acquisition/release patterns that stop improper shutdown from being introduced.

SC-6 Resource Availability partial match

Priority-based resource allocation limits the blast radius when released resources are not returned to the pool.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly include coding standards for correct resource allocation and release.

DE.CM-09 partial match
prevents

Runtime monitoring can detect resource exhaustion caused by improper shutdown or release.

ID.AM-08 partial match
prevents

Lifecycle management of assets can encompass proper resource release at end-of-life or shutdown.

PR.IR-04 partial match
prevents

Capacity management helps surface leaks from unreleased resources but does not prevent the coding flaw.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.5.37 Documented operating procedures partial match
prevents

Including restart, recovery and media-handling instructions reduces the likelihood that resources or sensitive data will be left in an exposed or improperly released state after a failure.

References