CVE-2026-133702 in free5GCinfo

Summary

by MITRE • 11/20/2026

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 Npcf_PolicyAuthorization 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.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Analysis

by VulDB Data Team • 11/20/2026

The vulnerability identified in free5GC versions through 1.4.6 represents a significant resource management flaw within the Policy Control Function, specifically affecting the postAppSessCtxProcedure logic. This component is responsible for handling session context procedures related to policy authorization requests initiated by Application Functions. The core technical deficiency lies in the failure to properly release or clean up Packet Congestion and Charging (PCC) rules and Quality of Service data structures when an Npcf_PolicyAuthorization create request is rejected. Instead of discarding these resources upon a negative outcome, the system retains them within the SM policy decision context, leading to a progressive accumulation of stale state information in memory.

This architectural oversight creates a direct path for resource exhaustion attacks by authenticated Application Functions that possess knowledge of an active PDU session's User Equipment address. By exploiting this flaw, an attacker can send repeated failing requests characterized by distinct AF application identifiers. Each rejected request triggers the allocation and retention of policy data without subsequent cleanup, effectively causing unbounded memory growth within the PCF process. This behavior allows for a denial-of-service condition where the target system becomes increasingly resource-constrained over time due to the pollution of its internal policy database with invalid or obsolete entries.

From an operational impact perspective, this vulnerability compromises both the availability and integrity of network functions in 5G core environments. The continuous accumulation of PCC rules and QoS data not only degrades performance by consuming system memory but also risks polluting the policy decisions sent to the Session Management Function. If these corrupted or stale policies are propagated, they may result in incorrect traffic handling, unauthorized resource allocation, or service degradation for legitimate users sharing the same session context. The attack requires authentication and specific knowledge of active sessions, which limits its scope compared to unauthenticated exploits but still poses a severe threat within trusted internal networks where Application Functions operate.

The vulnerability aligns with CWE-401, which describes missing release of memory after effective usage, as well as CWE-772, referring to the lack of releasing resources after successful connection. In terms of offensive security frameworks, this behavior is consistent with ATT&CK technique T1496, or Resource Hijacking, where an adversary consumes system resources to degrade service availability. Mitigation strategies should prioritize upgrading free5GC to a version later than 1.4.6 where the postAppSessCtxProcedure has been patched to ensure proper deallocation of PCC rules and QoS data upon request rejection. Additionally, implementing strict rate limiting on policy authorization requests per application identifier can help mitigate the impact by preventing rapid successive calls that trigger the leak. Network operators should also monitor PCF memory usage patterns for anomalies indicative of this specific resource exhaustion pattern.

Responsible

VulnCheck

Reservation

11/20/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00419

KEV

no

Activities

very low

Sources

Want to stay up to date on a daily basis?

Enable the mail alert feature now!