# CVE-2026-8782: omec-project amf NGAP Message handler.go null pointer dereference

> Remote attackers can cause a denial of service via null pointer dereference in the NGAP Message Handler of the omec-project AMF.

- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 May 2026
- **Updated:** 18 May 2026
- **Also known as:** GHSA-6h8r-h22r-jj64, GO-2026-5179

## What is CVE-2026-8782?

CVE-2026-8782 is a medium-severity vulnerability in omec-project amf, published on 18 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A weakness has been identified in omec-project amf up to 2.1.3-dev. This affects an unknown function of the file ngap/handler.go of the component NGAP Message Handler. This manipulation causes null pointer dereference. Remote exploitation of the attack is possible. The exploit has been made available to the public and could be used for attacks. Upgrading to version 2.2.0 mitigates this issue. It is recommended to upgrade the affected component. The same pull request fixes multiple security issues.

Weakness: CWE-476 (NULL Pointer Dereference), CWE-404 (Improper Resource Shutdown or Release)

## Which versions are affected by CVE-2026-8782?

3 open source packages ship an affected version, including github.com/omec-project/amf.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/omec-project/amf` | Go | All versions | None |
| `github.com/omec-project/amf` | Go | All versions | 2.2.0 |
| `github.com/omec-project/amf` | Go | All versions | 2.2.0 |

## How do I fix CVE-2026-8782?

Upgrade github.com/omec-project/amf to 2.2.0 or later.

## Is CVE-2026-8782 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8782 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8782 and fix it if it is affected.

What it is: CVE-2026-8782 is a medium-severity vulnerability in omec-project amf, published on 18 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8782 exists.

Affected packages and fixed versions:
- github.com/omec-project/amf (Go): affected all versions; no fix listed
- github.com/omec-project/amf (Go): affected all versions; fixed in 2.2.0
- github.com/omec-project/amf (Go): affected all versions; fixed in 2.2.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-8782/ (Markdown: https://insights.sbomify.com/CVE-2026-8782/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-8782
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-8782
- OSV: https://osv.dev/vulnerability/CVE-2026-8782

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-8782/
Summaries are generated and may contain mistakes; the official description above is the record.