Quick answers
- Is CVE-2026-30051 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-30051 being exploited in the wild.
- How severe is CVE-2026-30051?
- High severity, with a CVSS score of 7.5, published 27 August 2026.
- Which products and versions are affected?
- free5GC v4.1.0.
- Is there a fix for CVE-2026-30051?
- 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-30051 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-30051?
- 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
A missing bounds check in the CreateUEContextProcedure function (/namf-comm/v1/ue-contexts/{supi} endpoint) causes an out-of-bounds array access panic. The vulnerable code attempts to read ueContextCreateData.UeContext.RestrictedRatList[0] without verifying the array contains elements. An unauthenticated attacker can send a PUT request with an empty or omitted RestrictedRatList field, triggering a runtime panic that crashes the AMF process. The attack requires network access to the AMF service port (typically 8000) but does not require authentication. Fix: upgrade to patched version or validate RestrictedRatList length before indexing.
Affected products
- free5gc free5gc v4.1.0
Timeline
- 2026-01-06: disclosed
- 2026-08-27: advisory