CVE-2026-134658 in free5GCinfo

Summary

by MITRE • 11/22/2026

free5GC SMF through 1.4.6 contains a missing resource release vulnerability in HandlePDUSessionSMContextCreate that leaves CHF charging sessions open when PCF session rule application fails. Attackers can repeatedly trigger failed PDU session establishments to accumulate orphaned charging sessions on the CHF and degrade its availability.

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

Analysis

by VulDB Data Team • 11/22/2026

The free5GC implementation of the Session Management Function, specifically in versions up to 1.4.6, exhibits a critical resource management flaw within the HandlePDUSessionSMContextCreate procedure. This vulnerability stems from an incomplete error handling mechanism that fails to properly release associated resources when specific downstream interactions encounter failures. In the context of 5G core network architecture, the SMF is responsible for session establishment and modification, often interacting with the Policy Control Function (PCF) to determine policy rules and charging parameters before finalizing a PDU session. When the PCF fails to apply or return necessary session rules due to configuration errors, connectivity issues, or internal processing faults, the SMF initiates an abort sequence for that specific session context. However, in this vulnerable version, while the local session context is discarded, the corresponding charging sessions established with the Charging Function (CHF) are not terminated. This asymmetry results in orphaned charging records remaining active on the CHF despite the PDU session never being successfully established or subsequently failing during setup.

This technical flaw directly impacts the availability and integrity of the Charging Function within the 5G core network infrastructure. Since each failed attempt leaves a residual charging session open, an attacker can exploit this by repeatedly triggering PDU session establishment requests that are destined to fail due to PCF rule application errors. This constitutes a form of resource exhaustion attack where the CHF accumulates stale or orphaned sessions over time. As these unused resources consume memory and processing capacity on the CHF, the overall performance degrades significantly. In severe cases, this can lead to service denial for legitimate users who require charging services, as the CHF may become unable to process new requests due to resource saturation. The vulnerability effectively allows a remote attacker with access to the N1 or N2 interfaces, or potentially through compromised user equipment, to degrade network availability without needing authentication credentials if proper input validation is not enforced at earlier stages.

From a classification perspective, this issue aligns with CWE-403: Excessive Resource Locking and CWE-756: Missing Custom Error Handling. The failure to release resources upon error conditions represents a classic logic flaw where the cleanup path diverges from the success path in terms of resource lifecycle management. Furthermore, within the MITRE ATT&CK framework for Enterprise, this behavior is indicative of T1498 Network Denial of Service, specifically through endpoint exhaustion or service degradation via repeated failed interactions that consume backend resources. The attack vector relies on the ability to induce state changes in the SMF and CHF without completing the transaction, highlighting a gap in the atomicity of session management operations across multiple network functions.

Mitigation strategies must focus on ensuring strict resource cleanup protocols are enforced regardless of the outcome of downstream function interactions. Developers should implement robust error handling within the HandlePDUSessionSMContextCreate routine to guarantee that any charging sessions initiated with the CHF during the PDU session establishment phase are explicitly terminated if the PCF rule application fails or times out. This may involve implementing a transaction rollback mechanism or explicit API calls to cancel pending charging requests before discarding the SM context. Additionally, network operators should consider deploying rate limiting on PDU session establishment requests at the AMF or UPF level to mitigate the impact of such attacks in environments where immediate patching is not feasible. Upgrading to free5GC versions greater than 1.4.6, which include fixes for this resource leak, remains the most effective long-term solution. Regular auditing of charging sessions and monitoring for anomalies in CHF resource usage can also aid in early detection of exploitation attempts.

Responsible

VulnCheck

Reservation

11/22/2026

Disclosure

11/22/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Want to stay up to date on a daily basis?

Enable the mail alert feature now!