Is there a public PoC exploit available for EUVD-2026-41663?

Yes, a public proof-of-concept exploit is available for EUVD-2026-41663. Prioritise patching immediately. EPSS: 0.3%.

Is there a patch available for EUVD-2026-41663?

Yes, a patch is available for EUVD-2026-41663. Update the affected software to the latest version immediately.

omec-project AMF EUVD-2026-41663

Q: What is the CVSS score of EUVD-2026-41663?

EUVD-2026-41663 has a CVSS 4.0 base score of 2.1 (Low). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/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 exploitation probability: 0.3%.

| CVE-2026-14624 LOW

Improper Resource Shutdown or Release (CWE-404)

2026-07-04 VulDB

GHSA-rq3q-xf6q-wrpm

Denial Of Service Amf Omec Project

2.1

CVSS 4.0 · Vendor: VulDB

Severity by source

Vendor (VulDB) PRIMARY

2.1 MEDIUM

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/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

vuln.today AI

4.3 MEDIUM

Network-reachable via NGAP with low-privilege N2 access required (PR:L); only partial local availability impact; no confidentiality or integrity effect.

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

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Severity Changed

Jul 04, 2026 - 11:22 NVD

MEDIUM LOW

CVSS changed

Jul 04, 2026 - 11:22 NVD

5.3 (MEDIUM) 2.1 (LOW)

Analysis Generated

Jul 04, 2026 - 11:21 vuln.today

DescriptionCVE.org

A vulnerability was identified in omec-project amf up to 2.0.2/2.1.1. Impacted is an unknown function of the file /go/src/amf/ngap/handler.go of the component NGSetupRequest Handler. The manipulation leads to denial of service. It is possible to initiate the attack remotely. The exploit is publicly available and might be used. The identifier of the patch is 34bc6724acc97dba1f8691e586da95b042cb612d. To fix this issue, it is recommended to deploy a patch.

AnalysisAI

Denial of service in omec-project's 5G Access and Mobility Management Function (AMF) versions up to 2.0.2 and 2.1.1 allows remote low-privileged attackers to crash the AMF process by sending a malformed NGSetupRequest message over the NGAP interface. A publicly available proof-of-concept exploit exists via GitHub issue #677, lowering the exploitation barrier substantially. No CISA KEV listing exists, but given the AMF's role as the central mobility and registration anchor in 5G core infrastructure, even a partial service disruption can deny connectivity across entire served cell areas.

Technical ContextAI

The omec-project AMF is an open-source Go implementation of the 3GPP-defined 5G Core Access and Mobility Management Function, used in cloud-native and research 5G deployments. The vulnerable code resides in /go/src/amf/ngap/handler.go, specifically in the handler for NGSetupRequest messages - the initial NGAP (NG Application Protocol) handshake sent by 5G gNodeBs (base stations) over the N2 interface to establish control-plane connectivity with the AMF. CWE-404 (Improper Resource Shutdown or Release) identifies the root cause class: the handler fails to properly close, release, or deallocate resources when processing unexpected or malformed NGSetupRequest payloads, leading to a crash or resource exhaustion. The CPE cpe:2.3:a:omec-project:amf:*:*:*:*:*:*:*:* covers all versions of this component. In 5G networks, the N2 interface carrying NGAP is typically SCTP-based and isolated on a dedicated RAN-facing network segment, but cloud-native deployments may have weaker segmentation.

RemediationAI

Apply the upstream fix available as commit 34bc6724acc97dba1f8691e586da95b042cb612d, introduced via GitHub pull request #666 at https://github.com/omec-project/amf/pull/666. A specific tagged release version confirmed to incorporate this fix was not identified in available data - operators should verify the commit is present in their deployed build by checking the repository's release history or commit log. As a compensating control pending patch application, restrict access to the AMF's N2/NGAP interface (typically SCTP port 38412) via firewall ACLs or network policy to known, authorized gNodeB IP addresses only; this limits the attacker pool to trusted RAN infrastructure and substantially reduces exploitation risk without impacting legitimate traffic. In Kubernetes-based 5G core deployments, enforce NetworkPolicy to permit NGAP traffic only from gNodeB-namespace pods.