Is CVE-2026-9300 exploited in the wild?

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

How severe is CVE-2026-9300?

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

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

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

Am I affected by CVE-2026-9300?

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-9300: omec-project amf memory corruption in NGSetupRequest Handler

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

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

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

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

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-9300 · 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 memory corruption issue. An attacker can send specially crafted network registration requests to crash the service, potentially leading to a denial of service for mobile subscribers. This impact could disrupt connectivity and network operations for affected users.

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

Quick answers

Is CVE-2026-9300 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-9300 being exploited in the wild.
How severe is CVE-2026-9300?: 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-9300?: 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-9300 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-9300?: 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 memory corruption vulnerability exists in the omec-project AMF (Access and Mobility Management Function) within the NGSetupRequest Handler and NAS conversion components. The flaw is triggered by improper restriction of operations within the bounds of a memory buffer (CWE-119) when handling a RegistrationRequest with an invalid SUCI (Subscription Concealed Identifier) format. Specifically, the `nasConvert.SuciToString` function can encounter an out-of-bounds index error (e.g., index -1) when attempting to convert malformed MobileIdentity data. A remote attacker with low privileges can exploit this by sending a crafted InitialUEMessage, leading to a service panic and crash. The issue is addressed in version 1.7.1-0.20260421213846-34bc6724acc9 and later.

Affected products

omec-project amf < 1.7.1-0.20260421213846-34bc6724acc9

Identifiers

CVE-2026-9300
GHSA-6p7m-c3mw-4gmw
GO-2026-5842

Timeline

2026-04-21: patched: Fix merged in pull request 666
2026-04-23: disclosed: Public issue report on GitHub
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.