Quick answers
- Is CVE-2026-82587 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82587 being exploited in the wild.
- How severe is CVE-2026-82587?
- Medium severity, with a CVSS score of 4.3, published 30 August 2026.
- Which products and versions are affected?
- Open5GS up to 2.7.7.
- Is there a fix for CVE-2026-82587?
- A patch was published on 2026-05-14: Patch commit abf8a836564b966b5141110fc25ed413c4f17522 authored Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-82587 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-82587?
- Check whether you run Open5GS 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
The vulnerability is a memory corruption flaw in the amf_namf_comm_decode_ue_mm_context_list function of src/amf/namf-handler.c within the AMF component. Improper handling of the ueContext.mmContextList[*].allowedNssai argument leads to memory corruption. The vulnerability is remotely exploitable and requires no authentication; however, successful exploitation may depend on network-level access to the AMF service. An attacker can trigger a denial of service by crashing the AMF process. The issue is resolved in version 2.8.0 via commit abf8a836564b966b5141110fc25ed413c4f17522, which improves error handling in namf handlers.
Affected products
- Open5GS Open5GS up to 2.7.7
Timeline
- 2026-08-30: disclosed: CVE-2026-82587 published
- 2026-05-14: patched: Patch commit abf8a836564b966b5141110fc25ed413c4f17522 authored
- 2026-05-13: other: Patch authored