Quick answers
- Is CVE-2026-30059 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-30059 being exploited in the wild.
- How severe is CVE-2026-30059?
- High severity, with a CVSS score of 7.5, published 27 August 2026.
- Which products and versions are affected?
- free5GC v4.0.1.
- Is there a fix for CVE-2026-30059?
- 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-30059 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-30059?
- Check whether you run free5GC 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 an index-out-of-bounds (panic) in the NAS decoder component of free5gc when parsing the 5GSID Information Element within a 5GMMRegistrationRequest message. The root cause is insufficient length validation during NAS message parsing. An attacker can craft an InitialUEMessage where the 5GSID IE declares a length (L) that does not match the actual content length (e.g., declaring length 5 while content is longer), causing an "index out of range" panic when the parser attempts to read beyond the declared bounds. This panic crashes the AMF process immediately, resulting in complete DoS. The attack requires network reachability to the AMF's NGAP interface but no authentication or user interaction. Patches are available in free5gc versions after v4.0.1.
Affected products
- free5gc free5gc v4.0.1
Timeline
- 2026-01-18: disclosed: Issue reported on GitHub
- 2026-08-27: advisory: CVE published