Quick answers
- Is CVE-2026-8783 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-8783 being exploited in the wild.
- How severe is CVE-2026-8783?
- 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-8783?
- 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-8783 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-8783?
- 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 exists in the omec-project AMF (Access and Mobility Management Function) within the UERadioCapabilityCheckResponse function in ngap/dispatcher.go. The vulnerability is triggered when the NGAP dispatcher fails to properly validate malformed or incomplete NGAP PDUs, leading to a panic during message handling. A remote attacker with the ability to send NGAP messages to the AMF can exploit this to cause a denial-of-service (DoS) by crashing the service. The issue was addressed in version 2.2.0 by implementing comprehensive nil-pointer and bounds checks across the NGAP and NAS handlers.
Affected products
- omec-project amf < 2.2.0
Identifiers
- CVE-2026-8783
- GHSA-6v92-ph9p-hrpc
- GO-2026-5190
Timeline
- 2026-04-21: patched: Fix merged in pull request 666
- 2026-04-23: disclosed: Public issue report with reproduction steps published
- 2026-05-18: advisory: GitHub Advisory and CVE published