CVE-2026-8781VulnerabilityPublished 18 May 2026

CVE-2026-8781: omec-project amf · NULL Pointer Dereference

Affects omec-project amfSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
omec-projectamf	Affected =2.1.3-dev	Fixed in–
GitHubomec-project/amf`pkg:github/omec-project/amf`Other threats	Affected =2.1.3-dev	Fixed in–

CPE configurations (1)

cpe:2.3:a:omec-project:amf:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrading the omec-project amf component to version 2.2.0 fully resolves this vulnerability along with other security issues. Applying this official fix is the recommended remediation. Since this is not a cloud service, users must manually upgrade their deployments. Patch status is confirmed by the vendor's release notes indicating version 2.2.0 as the fix. No alternative mitigations or temporary workarounds are indicated.

Description

A security flaw has been discovered in omec-project amf up to 2.1.3-dev. The impacted element is the function RANConfiguration of the file ngap/handler.go. The manipulation results in null pointer dereference. The attack may be launched remotely. The exploit has been released to the public and may be used for attacks. Upgrading to version 2.2.0 is sufficient to resolve this issue. Upgrading the affected component is recommended. The same pull request fixes multiple security issues.

Impact

Successful exploitation of this vulnerability can cause the affected application to crash or behave unexpectedly due to null pointer dereference. This may lead to denial of service conditions. There is no indication of privilege escalation, data disclosure, or code execution from the provided data. The vulnerability can be triggered remotely without authentication, increasing its risk profile. Public exploit availability raises the likelihood of attacks against unpatched systems.

Summary

The vulnerability CVE-2026-8781 affects the omec-project amf software versions up to 2.1.3-dev. It is caused by a null pointer dereference in the RANConfiguration function of the ngap/handler.go file. This flaw can be exploited remotely without authentication or user interaction, potentially causing a denial of service or application crash. Public exploit code is available, increasing the risk of exploitation. The issue is fixed by upgrading to version 2.2.0, which includes a pull request that also addresses other security issues.

References

Community reviews

Loading reviews…