Quick answers
- Is CVE-2026-30073 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-30073 being exploited in the wild.
- How severe is CVE-2026-30073?
- 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-30073?
- 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-30073 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-30073?
- 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 NssaiAvailabilitySubscriptionCreate request handler in free5gc v4.0.1 contains a nil pointer dereference vulnerability. The handler accesses and mutates a shared global configuration object (factory.NssfConfig.Subscriptions) without initializing it or implementing synchronization, causing a panic when dereferencing uninitialized pointers, maps, or slices. An unauthenticated attacker can trigger this by sending a crafted POST request to the /nnssf-nssaiavailability/v1/nssai-availability/subscriptions endpoint, resulting in a runtime panic (HTTP 500) and immediate service crash. The attack requires no authentication and only network reachability to the NSSF service. A patch or upstream fix is required to add proper initialization and synchronization to the shared state access.
Affected products
- free5gc free5gc v4.0.1
Timeline
- 2026-01-01: disclosed: Vulnerability reported via GitHub issue #764
- 2026-08-27: advisory: CVE-2026-30073 published