Service crash via missing UE context
Published May 23, 2026 · Updated May 23, 2026
Nil-pointer dereference in Aether SD-Core AMF 2.1.0 through 2.1.1 allows remote authenticated users to crash the service. FetchRanUeContext accepts a PathSwitchRequest without an established UE context and dereferences the resulting nil pointer. An NGAP peer with network access can send the published packet to terminate the AMF process, interrupting 5G control-plane service.
Summary
What happened
Nil-pointer dereference in Aether SD-Core AMF 2.1.0 through 2.1.1 allows remote authenticated users to crash the service. FetchRanUeContext accepts a PathSwitchRequest without an established UE context and dereferences the resulting nil pointer. An NGAP peer with network access can send the published packet to terminate the AMF process, interrupting 5G control-plane service.
The record
- CVE
- CVE-2026-9298
- Published
- May 23, 2026
- Updated
- May 23, 2026
- Vendor
- Aether SD-Core Project
- Product
- AMF
- Classifications
- CWE-119, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 23, 2026CVE publishedPublication date reported by the CVE source.
- May 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.1.0
- Affected versionversion=2.1.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- PathSwitchRequest missing-UE-context crash packetproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo