Quick answers
- Is CVE-2026-8782 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-8782 being exploited in the wild.
- How severe is CVE-2026-8782?
- Medium severity, with a CVSS score of 4.3, published 18 May 2026.
- Which products and versions are affected?
- github.com/omec-project/amf (Go) < 2.2.0, SEMVER:introduced=0, SEMVER:introduced=0,fixed=2.2.0; OMEC Project AMF < 2.2.0, up to 2.1.3-dev.
- Is there a fix for CVE-2026-8782?
- Yes. github.com/omec-project/amf (Go): upgrade to 2.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-8782 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-8782?
- Check whether you run github.com/omec-project/amf (Go) or OMEC Project AMF at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- github.com/omec-project/amf (Go): upgrade to 2.2.0 or later
go get github.com/omec-project/amf@v2.2.0
Technical details
A null pointer dereference vulnerability exists in the NGAP (Next Generation Application Protocol) message handler of the omec-project AMF. Specifically, the `HandleLocationReportingFailureIndication` function in `ngap/handler.go` fails to properly validate malformed NGAP messages, such as those with missing or invalid Information Elements (IEs). A remote attacker with network access to the AMF can send a crafted `LocationReportFailureIndication` message to trigger a panic (SIGSEGV), leading to a denial-of-service (DoS) condition. This issue was addressed in version 2.2.0 by implementing comprehensive nil-pointer checks and input validation across the NGAP dispatcher and NAS security parsing components.
Affected products
- omec-project amf < 2.2.0
Identifiers
- CVE-2026-8782
- GHSA-6h8r-h22r-jj64
- GO-2026-5179
Timeline
- 2026-04-21: patched: Pull request 666 merged to address crashes
- 2026-04-23: other: Issue 674 opened with reproduction steps
- 2026-05-18: advisory: GHSA and CVE published