Description
free5GC is an open-source implementation of the 5G core network. Prior to 4.2.2, free5GC's NEF mounts the 3gpp-pfd-management API without inbound OAuth2/bearer-token authorization. A network attacker who can reach NEF on the SBI can create, read, and delete PFD-management transaction state with a forged or arbitrary bearer token (e.g. Authorization: Bearer not-a-real-token). The route group is also reachable even when the running config's ServiceList does not declare it, so operators who think they disabled the service via config are still exposed. This vulnerability is fixed in 4.2.2.
Affected products
free5gc: free5gc
References4
- github.com/free5gc/free5gc/security/advisories/GHSA-5f62-53r8-q… ExploitVendor Advisory
- github.com/free5gc/free5gc/security/advisories/GHSA-5f62-53r8-q… ExploitVendor Advisory
- github.com/free5gc/free5gc/issues/858 ExploitIssue Tracking
- github.com/free5gc/nef/pull/23 Issue Tracking
Metrics
- CVSS 3.1
-
9.4
CRITICAL
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H - EPSS — exploit probability
- 0% percentile: 25 · as of 14 November 2026
- CWE
- CWE-862
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.