Is CVE-2026-8779 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-8779 being exploited in the wild.

How severe is CVE-2026-8779?

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-8779?

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-8779 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-8779?

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.

CVE-2026-8779: omec-project amf denial of service in NGSetupRequest

Q: Is there a fix for CVE-2026-8779?

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.

Q: How is CVE-2026-8779 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-8779?

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.

CVE-2026-8779 · Severity: medium · CVSS 4.3 · Published 2026-05-18

The Access and Mobility Management Function (AMF) component of the OMEC Project, which manages mobile network connections, is vulnerable to a denial-of-service attack. By sending a specially crafted network setup request, an attacker can cause the service to crash. This disruption can prevent mobile devices from connecting to the network, impacting service availability.

Technologies: github.com/omec-project/amf (Go), OMEC Project AMF. Vendors: Go, OMEC Project.

Quick answers

Is CVE-2026-8779 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-8779 being exploited in the wild.
How severe is CVE-2026-8779?: 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-8779?: 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-8779 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-8779?: 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 vulnerability exists in the omec-project AMF (Access and Mobility Management Function) up to version 2.1.3-dev. The flaw is located in the HandleNGSetupRequest function within ngap/handler.go, where the application fails to properly validate the InformationElement argument. Specifically, a malformed NGSetupRequest with missing or invalid information elements triggers a nil pointer dereference or an out-of-bounds memory access, leading to a Go runtime panic and service crash. This can be exploited remotely by an authenticated attacker (or a device with network access to the AMF) to cause a Denial of Service (DoS). The issue is addressed in version 2.2.0 by adding nil checks and input validation across the NGAP dispatcher and handlers.

Affected products

omec-project amf < 2.2.0

Identifiers

CVE-2026-8779
GHSA-fxvj-wqv2-xgcq
GO-2026-5386

Timeline

2026-04-21: patched: Fix merged in pull request 666
2026-04-23: disclosed: Issue 671 opened with reproduction steps
2026-05-18: advisory: GitHub Advisory and CVE published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.