CVE-2026-42083: Free5GC PCF: Missing authentication middleware in Npcf_SMPolicyControl allows access to SM policy handlers and disclosure of subscriber SUPI
Summary PCF NpcfSMPolicyControl missing authentication middleware allows unauthenticated access to SM policy handlers and disclosure of subscriber SUPI Details In NewServer(), the smPolicyGroup route group is created and routes are applied without attaching the router authorization middleware.
Published May 7, 2026 · Updated Jun 8, 2026
Affected packages
github.com/free5gc/pcf
- Ecosystem
- Go
- Affected
- < 1.4.3
- Fixed in
- 1.4.3
- Check
go list -m github.com/free5gc/pcf
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
PCF Npcf_SMPolicyControl missing authentication middleware allows unauthenticated access to SM policy handlers and disclosure of subscriber SUPI
Details
In NewServer(), the smPolicyGroup route group is created and routes are applied without attaching the router authorization middleware. In contrast, other PCF service groups such as Npcf_PolicyAuthorization do attach RouterAuthorizationCheck before route registration.
Because the middleware is missing, requests to the following endpoints can reach business logic even when no valid OAuth token is provided:
POST /npcf-smpolicycontrol/v1/sm-policiesGET /npcf-smpolicycontrol/v1/sm-policies/{smPolicyId}POST /npcf-smpolicycontrol/v1/sm-policies/{smPolicyId}/updatePOST /npcf-smpolicycontrol/v1/sm-policies/{smPolicyId}/delete
This is visible at runtime because unauthenticated requests return business-level responses such as 400 or 404 instead of being rejected with 401 before handler execution. Under valid lab preconditions (existing UE/session context and related policy data), unauthenticated POST /sm-policies can succeed with 201, and unauthenticated GET /sm-policies/{id} can succeed with 200 and return policy context containing subscriber identifiers including supi.
The root cause is missing router auth enforcement for Npcf_SMPolicyControl. Upstream also fixed this by adding RouterAuthorizationCheck to smPolicyGroup (and uePolicyGroup) in free5gc/pcf PR #63.
PoC
- Deploy free5GC with PCF reachable on the SBI network.
- Use the PoC against the PCF service without an
Authorizationheader: ```bash go run /home/ubuntu/free5gc/tools/npcf-smpolicy-noauth-poc/main.go \ --pcf-root /home/ubuntu/free5gc/NFs/pcf \ --pcf-url http://10.100.200.9:8000 \ --timeout 4s
Observe that unauthenticated requests to Npcf_SMPolicyControl return business responses instead of 401.
Impact
This is an authentication/authorization bypass on a network-accessible SBI service. Any unauthenticated actor able to reach the PCF SBI interface can invoke Npcf_SMPolicyControl handlers directly.
Credited to LinZiyuu.
References
- https://github.com/free5gc/free5gc/security/advisories/GHSA-6rgm-gr97-x3j5
- https://github.com/free5gc/free5gc/issues/844
- https://github.com/free5gc/pcf/pull/63
- https://github.com/free5gc/pcf/commit/8c4d457cdf58bb239ee30e88c56b370b22073964
- https://nvd.nist.gov/vuln/detail/CVE-2026-42083
- https://github.com/advisories/GHSA-6rgm-gr97-x3j5
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-44316
free5GC's PCF npcf-smpolicycontrol POST /sm-policies panics on downstream UDR/OpenAPI 404 via nil pointer dereference
high7.5May 8, 2026CVE-2026-44317
free5GC's PCF npcf-policyauthorization POST /app-sessions panics on suppFeat=1 with missing AfRoutReq via nil pointer dereference
medium6.5May 8, 2026CVE-2026-41135
free5GC PCF: Memory Leak via CORS Middleware Registration in HTTP Handler Leads to Denial of Service
high7.5Apr 22, 2026CVE-2025-60632
Free5GC is vulnerable to DoS through its Npcf_BDTPolicyControl POST API
medium6.5Nov 24, 2025
