Quick answers
- Is CVE-2026-30064 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-30064 being exploited in the wild.
- How severe is CVE-2026-30064?
- 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-30064?
- 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-30064 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-30064?
- 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 in the OAuth2 token handler (processor/processor.go, specifically the buildFilter function or HTTPAccessTokenRequest handler). When processing form data from POST requests to /oauth2/token, the code iterates through all key-value pairs and attempts to map them to struct fields using YAML tags. For unmatched form keys, the code leaves the field name as an empty string and attempts to set a value via reflect.FieldByName(""), which returns a zero reflect.Value. Calling .Set() on this zero value triggers a panic that crashes the goroutine. The attack requires only network access to the /oauth2/token endpoint and no authentication; a single malformed request can terminate the NRF (Network Repository Function) process, causing denial of service.
Affected products
- free5gc free5gc v4.0.1
Timeline
- 2026-01-06: disclosed: Issue #770 opened on GitHub
- 2026-08-27: advisory: CVE-2026-30064 published