Is CVE-2026-8780 exploited in the wild?

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

How severe is CVE-2026-8780?

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

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

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

Am I affected by CVE-2026-8780?

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-8780: Omec-project AMF denial of service via malformed NGAP message

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

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

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

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

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-8780 · Severity: medium · CVSS 4.3 · Published 2026-05-18

The Access and Mobility Management Function (AMF) in the OMEC Project, which handles mobile network signaling, is vulnerable to a denial-of-service attack. An attacker can send a specially crafted network message containing invalid characters to crash the service. This would disrupt mobile connectivity and network operations for users relying on this component.

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

Quick answers

Is CVE-2026-8780 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-8780 being exploited in the wild.
How severe is CVE-2026-8780?: 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-8780?: 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-8780 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-8780?: 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 in the NGAP Message Handler of the omec-project AMF (up to version 2.1.3-dev) allows for remote denial-of-service. The root cause is a failure to validate input strings in the 'ngap/dispatcher.go' and 'ngap/handler.go' components. Specifically, sending an NGSetupRequest containing a non-printable, non-UTF-8 string in the RANNodeName information element triggers a Go panic when the value is passed to the Prometheus metrics client. This leads to a service crash (memory corruption/panic). The issue is resolved in version 2.2.0 by implementing nil/empty checks and validating PLMN and NAS inputs.

Affected products

omec-project amf < 2.2.0

Identifiers

CVE-2026-8780
GHSA-3x4g-259h-5p7c
GO-2026-5104

Timeline

2026-04-21: patched: Pull request 666 merged to address crashes
2026-04-23: disclosed: Issue 670 reported with reproduction steps
2026-05-18: advisory: GHSA and CVE published

References

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