Is CVE-2026-9301 exploited in the wild?

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

How severe is CVE-2026-9301?

Medium severity, with a CVSS score of 6.3, published 23 May 2026.

Which products and versions are affected?

github.com/omec-project/amf (Go) < 1.7.1-0.20260421213846-34bc6724acc9, SEMVER:introduced=0,fixed=1.7.1-0.20260421213846-34bc6724acc9; OMEC Project AMF < 1.7.1-0.20260421213846-34bc6724acc9, up to 2.1.1.

Is there a fix for CVE-2026-9301?

Yes. github.com/omec-project/amf (Go): upgrade to 1.7.1-0.20260421213846-34bc6724acc9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-9301 attacked?

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

Am I affected by CVE-2026-9301?

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-9301: omec-project amf memory corruption in NGReset Message Handler

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

Yes. github.com/omec-project/amf (Go): upgrade to 1.7.1-0.20260421213846-34bc6724acc9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-9301 attacked?

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

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

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-9301 · Severity: medium · CVSS 6.3 · Published 2026-05-23

The omec-project Access and Mobility Management Function (AMF), a core component of 5G mobile networks, is vulnerable to a remote crash. By sending specially crafted network messages, an attacker can trigger a system failure (panic), leading to a denial of service for mobile subscribers. This could disrupt connectivity and network operations until the service is restarted.

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

Quick answers

Is CVE-2026-9301 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-9301 being exploited in the wild.
How severe is CVE-2026-9301?: Medium severity, with a CVSS score of 6.3, published 23 May 2026.
Which products and versions are affected?: github.com/omec-project/amf (Go) < 1.7.1-0.20260421213846-34bc6724acc9, SEMVER:introduced=0,fixed=1.7.1-0.20260421213846-34bc6724acc9; OMEC Project AMF < 1.7.1-0.20260421213846-34bc6724acc9, up to 2.1.1.
Is there a fix for CVE-2026-9301?: Yes. github.com/omec-project/amf (Go): upgrade to 1.7.1-0.20260421213846-34bc6724acc9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-9301 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-9301?: 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 1.7.1-0.20260421213846-34bc6724acc9 or later
```
go get github.com/omec-project/amf@v1.7.1-0.20260421213846-34bc6724acc9
```

Technical details

A vulnerability in the NGReset Message Handler of omec-project amf (up to version 2.1.1) allows for memory corruption and service crashes. The root cause is a nil pointer dereference in the `printAndGetCause` and `HandleNGReset` functions within `ngap/handler.go` when processing malformed NGAP packets. A remote attacker with network access can trigger a Go runtime panic by sending a crafted NGReset message with missing or invalid Information Elements (IEs). This issue was addressed in version 1.7.1-0.20260421213846-34bc6724acc9 (and later 2.2.0) by implementing proper nil checks and input validation across the NGAP dispatcher and handlers.

Affected products

omec-project amf < 1.7.1-0.20260421213846-34bc6724acc9

Identifiers

CVE-2026-9301
GHSA-qm7q-rcm2-3frc
GO-2026-5844

Timeline

2026-04-21: patched: Fix merged in pull request 666
2026-04-23: disclosed: Issue 678 reported with reproduction steps
2026-05-23: advisory: NVD publication date
2026-05-26: advisory: GitHub Advisory published

References

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