What is the CVSS score of CVE-2025-46115?

CVE-2025-46115 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. EPSS exploitation probability: 0.1%.

Which versions of Open5GS are affected by CVE-2025-46115?

CVE-2025-46115 is a critical denial-of-service vulnerability in Open5GS 2.7.3 that allows unauthenticated remote attackers to crash 5G core network infrastructure through malformed protocol messages,…

How to fix or mitigate CVE-2025-46115?

24 hours: Identify all Open5GS 2.7.3 deployments in production and isolate or restrict network access to PDU Session Modification Request handlers; document current versions and deployment topology. 7 days: Implement network-level filtering to block malformed PDU Session Modification Request messages at perimeter gateways; deploy intrusion detection signatures for CWE-20 input validation attacks; establish vendor contact channel with Open5GS for patch timeline. 30 days: Evaluate migration to alternative 5G core vendors with active security patching, or prepare for immediate patching upon vendor release; conduct load testing of any compensating controls.

Open5GS CVE-2025-46115

EUVD-2025-209598 HIGH

Improper Input Validation (CWE-20)

2026-04-30 mitre

Denial Of Service N A

7.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.5 HIGH

AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Lifecycle Timeline

Analysis Generated

May 04, 2026 - 18:22 vuln.today

CVSS changed

May 04, 2026 - 18:22 NVD

7.5 (HIGH)

EUVD ID Assigned

Apr 30, 2026 - 20:00 euvd

EUVD-2025-209598

Analysis Generated

Apr 30, 2026 - 20:00 vuln.today

CVE Published

Apr 30, 2026 - 00:00 nvd

HIGH 7.5

DescriptionCVE.org

An issue in open5gs v.2.7.3 allows a remote attacker to cause a denial of service via a crafted PDU Session Modification Request

AnalysisAI

Remote denial of service in Open5GS 2.7.3 allows unauthenticated attackers to crash the 5G core network by sending malformed PDU Session Modification Request messages. The vulnerability stems from improper input validation (CWE-20) in session management functions. EPSS score of 0.07% indicates low observed exploitation probability, and no active exploitation has been confirmed via CISA KEV. However, the attack requires no authentication or user interaction (AV:N/AC:L/PR:N/UI:N), making it trivially exploitable against exposed 5G core deployments, potentially disrupting mobile network services for enterprise or carrier environments.

Technical ContextAI

Open5GS is an open-source implementation of 5G Core and Evolved Packet Core (EPC) network functions. The vulnerability affects the Session Management Function (SMF) component responsible for handling PDU (Protocol Data Unit) Session lifecycle operations. The PDU Session Modification Request is a 3GPP-defined NAS (Non-Access Stratum) message used to modify established data sessions between user equipment and the 5G core. The root cause is CWE-20 (Improper Input Validation), indicating the SMF fails to properly sanitize or validate fields within incoming modification requests before processing them. CPE data shows 'n/a:n/a' which reflects incomplete vendor enumeration in NVD, but the GitHub issue confirms the specific affected product is Open5GS version 2.7.3. This affects deployments where the SMF interface is exposed to untrusted networks or compromised radio access equipment.

RemediationAI

Primary remediation requires monitoring the Open5GS GitHub repository (https://github.com/open5gs/open5gs) for a patch release addressing issue #3858, as no fixed version number is confirmed in available vendor advisories at time of analysis. Until an official patch is released, implement these specific compensating controls: (1) Deploy network-level filtering to restrict PDU Session Management messages to only trusted 5G RAN equipment using IPsec or TLS mutual authentication on N1/N2 interfaces, accepting the operational overhead of certificate management. (2) Enable strict input validation logging on SMF to detect malformed PDU Session Modification Requests and implement rate-limiting per UE (User Equipment) identifier to contain potential DoS impact, though this may introduce latency during legitimate high-volume session modifications. (3) Deploy SMF instances in high-availability clusters with health monitoring to enable automatic failover if a node crashes, which increases infrastructure cost but maintains service continuity. (4) For lab/test environments, isolate Open5GS deployments from production networks entirely and restrict access to authenticated VPN connections only. Subscribe to security notifications at https://github.com/open5gs/open5gs/security/advisories for official patch announcements.