Is there a public PoC exploit available for CVE-2026-14623?

Yes, a public proof-of-concept exploit is available for CVE-2026-14623. Prioritise patching immediately. EPSS: 0.5%.

Is there a patch available for CVE-2026-14623?

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

OMEC-Project AMF CVE-2026-14623

Q: What is the CVSS score of CVE-2026-14623?

CVE-2026-14623 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.5%.

EUVD-2026-41662 LOW

Improper Resource Shutdown or Release (CWE-404)

2026-07-04 VulDB

GHSA-8739-cv3v-hhgv

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-accessible NGAP endpoint requires low privilege (gNB access); impact is partial availability loss only, 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 - 10:22 NVD

MEDIUM LOW

CVSS changed

Jul 04, 2026 - 10:22 NVD

5.3 (MEDIUM) 2.1 (LOW)

Analysis Generated

Jul 04, 2026 - 10:21 vuln.today

DescriptionCVE.org

A vulnerability was determined in omec-project amf up to 2.1.1. This issue affects the function RRCInactiveTransitionReport of the component NGAP Message Handler. Executing a manipulation can lead to denial of service. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized. This patch is called 34bc6724acc97dba1f8691e586da95b042cb612d. A patch should be applied to remediate this issue.

AnalysisAI

Denial of service in omec-project AMF (Access and Mobility Management Function) versions up to 2.1.1 allows a low-privileged remote attacker to crash or degrade the NGAP Message Handler by submitting a crafted RRCInactiveTransitionReport message, exploiting improper resource release (CWE-404). The vulnerability affects the 5G core network control plane component responsible for UE mobility and session management, making it a high-value target in operator and research 5G deployments. No active exploitation is confirmed via CISA KEV, but a public proof-of-concept has been disclosed via GitHub issue #676 and a patch commit exists.

Technical ContextAI

The OMEC-Project AMF is an open-source implementation of the 5G core Access and Mobility Management Function, handling NGAP (Next Generation Application Protocol) messages exchanged over the N2 interface between gNBs (base stations) and the 5G core. The vulnerable function, RRCInactiveTransitionReport, processes Radio Resource Control (RRC) state transition notifications from the RAN. CWE-404 (Improper Resource Shutdown or Release) indicates the code fails to properly release or clean up internal resources when processing a manipulated version of this message, leading to resource exhaustion or state corruption that degrades service availability. The affected CPE is cpe:2.3:a:omec-project:amf:*:*:*:*:*:*:*:* covering all versions through 2.1.1.

RemediationAI

Apply the upstream fix commit 34bc6724acc97dba1f8691e586da95b042cb612d from GitHub pull request #666 (https://github.com/omec-project/amf/pull/666). This is a source-level patch; a tagged release version incorporating this fix has not been independently confirmed at time of analysis - operators should build from the patched commit or monitor for a versioned release. As a compensating control pending patch deployment, restrict access to the N2 interface (AMF's NGAP endpoint) to trusted gNB IP ranges using firewall or network policy rules, preventing unauthorized NGAP message injection. Additionally, consider deploying NGAP message validation or anomaly detection at the N2 interface perimeter. Note that N2 interface restriction may impact legitimate RAN connectivity and should be coordinated with network operations.