Is CVE-2026-9298 exploited in the wild?

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

How severe is CVE-2026-9298?

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

Is there a fix for CVE-2026-9298?

A patch was published on 2026-04-21: Pull request #666 merged to address crashes Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-9298 attacked?

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

Am I affected by CVE-2026-9298?

Check whether you run 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-9298: omec-project amf memory corruption in PathSwitchRequest Handler

CVE-2026-9298 · Severity: medium · CVSS 6.3 · Published 2026-05-23

A vulnerability exists in the Access and Mobility Management Function (AMF) of the omec-project, which is a core component of 5G mobile networks responsible for managing device connectivity and mobility. An attacker can send a specially crafted network request that causes the system to crash due to a memory handling error. This results in a denial-of-service condition, potentially disrupting mobile network services for users. The issue has been addressed in newer versions of the software.

Technologies: OMEC Project AMF. Vendors: OMEC Project.

Quick answers

Is CVE-2026-9298 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-9298 being exploited in the wild.
How severe is CVE-2026-9298?: Medium severity, with a CVSS score of 6.3, published 23 May 2026.
Which products and versions are affected?: OMEC Project AMF up to 2.1.1.
Is there a fix for CVE-2026-9298?: A patch was published on 2026-04-21: Pull request #666 merged to address crashes Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-9298 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-9298?: Check whether you run 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.

Technical details

A vulnerability in the PathSwitchRequest Handler and NGAP dispatcher of omec-project amf (up to version 2.1.1) allows for remote memory corruption, specifically a nil pointer dereference. The root cause is a failure to validate the existence of a User Equipment (UE) Context before processing certain NGAP packets, such as a PathSwitchRequest. An attacker with network access can trigger a Go runtime panic (SIGSEGV) by sending malformed NGAP/NAS inputs, leading to a denial-of-service. The vulnerability is addressed in version 2.2.1 by implementing nil checks and input validation across the NGAP dispatcher and NAS security parsing components.

Affected products

omec-project amf up to 2.1.1

Timeline

2026-04-21: patched: Pull request #666 merged to address crashes
2026-04-23: disclosed: Issue #680 reported with reproduction steps
2026-05-23: advisory: CVE-2026-9298 published

References

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