OMEC Project amf denial of service via crash in NGAP path switch handling
- Exploited
- No known exploitation
- Fix
- Fixed in 3.1.6
- Who is exposed
- Not reported
Summary
The Aether Project amf software can crash when it receives a malformed NGAP PathSwitchRequest, which terminates the AMF. An attacker reaches it over the network, needing high privileges and a registered UE's AMF-UE-NGAP-ID, typically from a rogue or compromised gNB on the N2 interface.
Written by a model
Original description
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 to do
Upgrade to a fixed version: 3.1.6.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-102945 (Aether Project amf: panic on an unrecovered NGAP goroutine), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-102945 (entry last updated 2026-11-19):
Affected:
- omec-project amf: fixed in 3.1.6
Fixed versions: 3.1.6.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-102945 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-102945 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/omec-project/amf/security/advisories/GHSA-v6w5-38cf-pcv8
- https://github.com/omec-project/amf/pull/767
- https://github.com/omec-project/amf/commit/d28042aaaea0221c5ea93c3e069a1dd5e7436f4c
- https://github.com/omec-project/amf/releases/tag/v3.1.6
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-102945
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-102945"}.Affected versions
- omec-project amffixed in 3.1.6
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.9/10CVSS 4.9
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · omec-project/amf · Advisory GHSA-v6w5-38cf-pcv8 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-102945 |
| Record | NVD · CVE-2026-102945 |
| Other links 3 | |
| Repository | GitHub · omec-project/amf · Pull request #767 |
| Repository | GitHub · omec-project/amf · Commit d28042aa |
| Repository | GitHub · omec-project/amf · Release v3.1.6 |
Questions about CVE-2026-102945
Is CVE-2026-102945 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-102945?
amf: before 3.1.6.
Source: cve.now feed data
How do I fix CVE-2026-102945?
Upgrade to a fixed version: 3.1.6.
Source: cve.now feed data
Related
- CVE-2026-14624omec-project amf NGSetupRequest handler.go denial of service
- CVE-2026-14623omec-project amf NGAP Message RRCInactiveTransitionReport denial of service
- CVE-2026-9301omec-project amf NGReset Message memory corruption
- CVE-2026-9300omec-project amf NGSetupRequest memory corruption
- CVE-2026-9299omec-project amf handler.go PDUSessionResourceModifyIndication memory corruption
- CVE-2026-9298omec-project amf PathSwitchRequest memory corruption
No corrections so far. Something wrong on this page? Report an error.