Skip to main content

CVE-2026-102945omec-project amf out-of-bounds read

Low priorityMedium4.9EPSS not scored yet

CVE-2026-102945 is a out-of-bounds read in omec-project amf, rated medium (4.9 on CVSS 3.1).

Why this priority: Medium severity, with no exploitation signal.

Published · Updated · NVD status: Received

What it is

Code reads past the end of a buffer, leaking memory contents or crashing. An error nobody catches stops the process or request.

How it is reached

An attacker can exploit it over the network, with an administrator account, and nobody has to click anything.

What an attacker gains

A successful attack can take it offline. In practice, this kind of flaw lets an attacker crash the process, read memory, or in the worst case run code.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. Upgrade omec-project amf to 3.1.6 or later.
  2. Until it is patched, review who holds accounts that can reach it.

Description from NVD

Aether Project AMF supports termination of NAS signalling, NAS ciphering & integrity protection, registration management, connection management, mobility management, access authentication and authorization, security context management. Prior to 3.1.6, a malformed NGAP PathSwitchRequest can contain a UESecurityCapabilities information element whose extensible APER bit-string representation has no bytes even though decoding reports no error. In ngap/handler.go, HandlePathSwitchRequest checks only whether the element is present before six index-zero reads of its encryption and integrity algorithm fields, causing an unrecovered panic in the NGAP receive goroutine and terminating the AMF. The described attacker is a rogue or compromised gNB on the N2 interface and additionally needs a registered UE's AMF-UE-NGAP-ID; a bare over-the-air UE cannot trigger the issue. This issue is fixed in version 3.1.6.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Native code: operating systems, browsers and firmware. The flaw sits wherever native code reads untrusted data.
  • Network appliances and media or file parsers. The flaw sits wherever native code reads untrusted data.
  • Public entry points and shared services that must stay up. The flaw sits between untrusted traffic and shared capacity.
  • Interfaces that accept external input. The flaw sits at the input boundary of the affected component.

Trust boundaries in play

  • Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
  • Wherever native code reads untrusted data. An attacker who crosses it can crash the process, read memory, or in the worst case run code.
  • Between untrusted traffic and shared capacity. An attacker who crosses it can exhaust CPU, memory or connections until the service stops answering.
  • At the input boundary of the affected component. An attacker who crosses it can drive the component into behaviour its authors did not intend.

Questions to answer about your own systems

  • Where does omec-project amf run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?

14-day free trial

Understand how your systems connect.

See your services, dependencies and trust boundaries in one place, with evidence from your connected environment.

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.