CVE-2026-44315: free5GC: NEF 3gpp-pfd-management API is unauthenticated; forged bearer tokens can create, read, and delete PFD transactions

Severity: critical (CVSS 9.4 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.3% probability of exploitation in the next 30 days
Public exploit or detection template: yes
Published: 2026-05-27 · updated 2026-10-14
Weakness: CWE-862

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: before 4.2.2 — fixed in 4.2.2

How to fix

Upgrade to a fixed version: free5gc 4.2.2. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2026-44315 or the next vulnerability affects your stack