Quick answers
- Is CVE-2026-30070 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-30070 being exploited in the wild.
- How severe is CVE-2026-30070?
- 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-30070?
- 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-30070 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-30070?
- 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 out-of-bounds array access in the HandleGetSharedData function of free5GC's UDM SDM module. The function assumes the 'supported-features' query parameter is present and attempts to access its first element (supportedFeatures[0]) without validating slice length or presence. When the parameter is omitted or empty, a Go runtime panic ("index out of range") is triggered, crashing the service and causing a denial of service. Attack vector is network-based; no authentication is required. A simple HTTP GET request to /nudm-sdm/v2/shared-data without the query parameter is sufficient to trigger the crash. Patches are expected to add proper validation of the supportedFeatures slice before access.
Affected products
- free5GC free5GC v4.0.1
Timeline
- 2026-01-01: disclosed: Bug reported on GitHub issue #762
- 2026-08-27: advisory: CVE-2026-30070 published