Quick answers
- Is CVE-2026-82552 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82552 being exploited in the wild.
- How severe is CVE-2026-82552?
- Medium severity, with a CVSS score of 4.3, published 30 August 2026.
- Which products and versions are affected?
- Linux Foundation Magma 1.9.0.
- Is there a fix for CVE-2026-82552?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-82552 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-82552?
- Check whether you run Linux Foundation Magma 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 context cleanup failure in the gNB Termination Handler component (ngap_amf.c). When a gNB disconnects or restarts, the AMF (Access and Mobility Management Function) fails to properly clear session contexts and RAN_UE_NGAP_ID identifiers from memory. This causes subsequent registration attempts with the same identifiers to fail with duplicate context errors, permanently blocking those identifiers until AMF restart. The vulnerability is network-reachable and requires no authentication; an attacker with network access to the gNB can trigger the condition by causing a gNB restart or disconnection. The fix requires proper context cleanup on gNB termination in the affected code paths (ngap_amf.c, ngap_amf_nas_procedure.c, and related handlers).
Affected products
- Linux Foundation Magma 1.9.0
Timeline
- 2026-07-15: disclosed: Issue reported on GitHub
- 2026-08-30: advisory: CVE-2026-82552 published