Quick answers
- Is CVE-2026-30068 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-30068 being exploited in the wild.
- How severe is CVE-2026-30068?
- 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-30068?
- 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-30068 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-30068?
- 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 HandleUpdate function in udm/internal/sbi/parameter_provision.go reads the entire HTTP request body using c.GetRawData() without enforcing size limits or implementing streaming. An attacker can send a PATCH request to /nudm-pp/v1/imsi-{id}/pp-data with an oversized payload, causing uncontrolled memory allocation that leads to out-of-memory errors and process termination (exit code 137). The vulnerability requires network access to the UDM endpoint, but no authentication bypass is needed if the endpoint is exposed or accessible within the network. A fix would involve implementing request size limits and rejecting requests exceeding a threshold with a 413 Payload Too Large response.
Affected products
- free5gc free5GC v4.0.1
Timeline
- 2026-01-01: disclosed: Issue reported on GitHub
- 2026-08-27: advisory: CVE-2026-30068 published