CVE-2026-44315 - free5GC's NEF 3gpp-pfd-management API is unauthenticated; forged bearer tokens c
CVE-2026-44315 - free5GC's NEF 3gpp-pfd-management API is unauthenticated; forged bearer tokens c
GHSA-5f62-53r8-qrqf CRITICAL go/github.com/free5gc/nef
CVE: CVE-2026-44315
Summary
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.
Details
Validated against the NEF container in the official Docker compose lab.
- Source repo tag:
v4.2.1 - Running Docker image:
free5gc/nef:v4.2.0 - Runtime NEF commit:
5ce35eab - Docker validation date: 2026-03-11
NEF advertises OAuth2 setting receive from NRF: true, and its ServiceList only declares nnef-pfdmanagement and nnef-oam. Despite that, the 3gpp-pfd-management route group is mounted and reachable with no inbound auth middleware.
Code evidence (paths in free5gc/nef):
- Route group mounted without auth middleware:
NFs/nef/internal/sbi/server.go:52 - Transaction routes exposed at
/:scsAsID/transactionsand/:scsAsID/transactions/:transID:NFs/nef/internal/sbi/api_pfd.go:13 - Create handler still contains
// TODO: Authorize the AF:NFs/nef/internal/sbi/processor/pfd.go:70 - POST allocates a new PFD transaction and writes to UDR:
NFs/nef/internal/sbi/processor/pfd.go:63 - GET reads transaction state:
NFs/nef/internal/sbi/processor/pfd.go:189 - DELETE removes transaction state:
NFs/nef/internal/sbi/processor/pfd.go:328 - NEF context only exposes outbound token acquisition (
GetTokenCtx); there is no inbound authorization path:NFs/nef/internal/context/nef_context.go:153 - Config validation only allows
nnef-pfdmanagementandnnef-oam:NFs/nef/pkg/factory/config.go:126
PoC
Reproduced end-to-end against the running NEF at http://10.100.200.19:8000 using a fabricated bearer token.
1. Seed an AF context (also accepted with
📌 来源: GitHub-Advisory | 🆔 CVE-2026-44315 | 📅 2026-05-08