CVE-2026-133702: free5GC PCF through 1.4.6 Orphaned PCC Rules via Rejected Application Session Creation
free5GC PCF through 1.4.6 contains a resource leak in postAppSessCtxProcedure that leaves PCC rules and QoS data in the SM policy decision after rejected NpcfPolicyAuthorization create requests. Authenticated AFs knowing an active PDU session's UE address can send repeated failing requests with distinct AF application identifiers to grow PCF memory and pollute policy sent to the SMF.
Affected Software
Event History
Frequently Asked Questions
Who can exploit this issue in practice?
An attacker needs to act as an authenticated AF and know the UE address for an active PDU session. Unauthenticated network clients are not described as able to trigger the flaw.
What conditions are needed to cause the resource leak?
The attacker must submit repeated Npcf_PolicyAuthorization create requests that fail, using distinct AF application identifiers. The affected PCF retains PCC rules and QoS data after those rejected requests.
What is the operational impact of repeated exploitation?
Repeated requests can grow PCF memory consumption and pollute the SM policy decision sent to the SMF. The reported impact includes integrity and availability effects.
How can teams determine whether they are affected?
Systems running free5GC PCF through version 1.4.6 are affected according to the report. Review PCF behavior for rejected PolicyAuthorization create requests that leave PCC rules or QoS data associated with the SM policy decision.