Quick answers
- Is CVE-2026-30071 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-30071 being exploited in the wild.
- How severe is CVE-2026-30071?
- 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-30071?
- 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-30071 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-30071?
- 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 improper input validation flaw (CWE-129: improper validation of array index) in the RechargePut function within the Converged Charging Handler (CHF) service. The function splits the rechargingInfo path parameter by underscore and immediately accesses the second element without checking the resulting slice length. A crafted PUT request to the /nchf-convergedcharging/v3/recharging/ endpoint with a parameter lacking an underscore triggers a runtime panic (index out of range), crashing the goroutine and causing the server to return HTTP 500. The attack requires only network access to the CHF endpoint and no authentication. A fix involves validating the slice length before array access.
Affected products
- free5gc free5gc v4.0.1
Timeline
- 2026-01-01: disclosed: Issue #760 opened on GitHub
- 2026-08-27: advisory: CVE-2026-30071 published