Description
A vulnerability was determined in omec-project amf up to 2.1.3-dev. Impacted is the function NGSetupRequest of the file ngap/handler.go. Executing a manipulation of the argument InformationElement can lead to memory corruption. The attack can be launched remotely. The exploit has been publicly disclosed and may be utilized. Upgrading to version 2.2.0 is recommended to address this issue. The affected component should be upgraded. The same pull request fixes multiple security issues.
Published: 2026-05-18
Score: 5.3 Medium
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability occurs in the NGSetupRequest function within the ngap/handler.go file of omec-project amf. A manipulation of the InformationElement argument can provoke memory corruption when the AMF processes an NGSetupRequest. The issue is described as a memory corruption bug that could destabilize the AMF or, potentially, enable more severe consequences such as code execution, though the official description does not explicitly claim this. The attack vectors that could exploit this flaw are described as remote. The vulnerability is publicly disclosed and may be used, indicating that an attacker can trigger the defect from outside the environment, for example by sending crafted NGSetupRequest messages. In terms of risk, the CVSS score is 5.3, which represents a medium severity. No EPSS data is currently available, and the vulnerability is not listed in the CISA KEV catalog. Because the exploit is remotely exploitable and publicly known, the overall threat remains non‑negligible and should be addressed promptly.

Affected Systems

Affected systems are those running omec-project amf versions up to 2.1.3-dev. The vulnerability exists in the NGSetupRequest handler and affects all deployments of the AMF component that host the ngap/handler.go logic. Administrators should verify that their AMF instances have not been upgraded beyond version 2.1.3-dev and plan a migration to version 2.2.0 or later for remediation.

Risk and Exploitability

The CVSS score of 5.3 indicates medium severity, reflecting a moderate impact on confidentiality, integrity, or availability. The EPSS score is not available, so current exploitation probability is unknown, but the vulnerability has been publicly disclosed and can be triggered remotely via crafted NGSetupRequest messages, indicating that an attacker can reach the flaw from outside the local network. Because it is not currently listed in the CISA KEV catalog, there is no confirmed widespread exploitation, yet the remote nature and public disclosure mean the risk remains non‑negligible and should be managed with timely patching.

Generated by OpenCVE AI on May 18, 2026 at 02:50 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade omec-project amf to version 2.2.0 or later to eliminate the memory corruption bug.
  • Restart the AMF service so the updated code is loaded and running.
  • Monitor AMF logs for abnormal NGSetupRequest activity and apply firewall rules to block or rate‑limit suspicious requests from untrusted origins.

Generated by OpenCVE AI on May 18, 2026 at 02:50 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 18 May 2026 01:30:00 +0000

Type Values Removed Values Added
Description A vulnerability was determined in omec-project amf up to 2.1.3-dev. Impacted is the function NGSetupRequest of the file ngap/handler.go. Executing a manipulation of the argument InformationElement can lead to memory corruption. The attack can be launched remotely. The exploit has been publicly disclosed and may be utilized. Upgrading to version 2.2.0 is recommended to address this issue. The affected component should be upgraded. The same pull request fixes multiple security issues.
Title omec-project amf handler.go NGSetupRequest memory corruption
First Time appeared Omec-project
Omec-project amf
Weaknesses CWE-119
CPEs cpe:2.3:a:omec-project:amf:*:*:*:*:*:*:*:*
Vendors & Products Omec-project
Omec-project amf
References
Metrics cvssV2_0

{'score': 4, 'vector': 'AV:N/AC:L/Au:S/C:N/I:N/A:P/E:POC/RL:OF/RC:C'}

cvssV3_0

{'score': 4.3, 'vector': 'CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L/E:P/RL:O/RC:C'}

cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L/E:P/RL:O/RC:C'}

cvssV4_0

{'score': 5.3, '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'}


Subscriptions

Omec-project Amf
cve-icon MITRE

Status: PUBLISHED

Assigner: VulDB

Published:

Updated: 2026-05-18T01:15:12.132Z

Reserved: 2026-05-17T09:55:52.168Z

Link: CVE-2026-8779

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-05-18T02:16:37.180

Modified: 2026-05-18T02:16:37.180

Link: CVE-2026-8779

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-05-18T03:00:13Z

Weaknesses