Quick answers
- Is CVE-2026-86212 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86212 being exploited in the wild.
- How severe is CVE-2026-86212?
- Medium severity, with a CVSS score of 4.3, published 6 September 2026.
- Which products and versions are affected?
- Open5GS 2.7.7, 2.8.0.
- Is there a fix for CVE-2026-86212?
- A patch was published on 2026-09-06: Patch available at commit 9468de94caed2fc940f4a23cbf734651896d0fde Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-86212 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-86212?
- 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
An improper authorization vulnerability exists in Open5GS versions 2.7.7 and 2.8.0 within the AMF and MME components. The vulnerability arises from insufficient validation of UE (User Equipment) associations during partial NG RESET and S1 RESET operations. An attacker can remotely exploit this by sending specially crafted reset messages that are not properly authenticated, allowing them to manipulate UE context associations or access resources without proper authorization. The fix involves validating that UE contexts referenced in reset operations belong to the requesting gNB/eNB and that core-network and RAN identifiers refer to the same UE association. A patch has been released and is available at commit 9468de94caed2fc940f4a23cbf734651896d0fde.
Affected products
- Open5GS Open5GS 2.7.7, 2.8.0
Timeline
- 2026-09-06: disclosed
- 2026-09-06: patched: Patch available at commit 9468de94caed2fc940f4a23cbf734651896d0fde