CVE-2026-133703 in Open5GSinfo

Summary

by MITRE • 11/20/2026

Open5GS AMF through 2.8.0 contains a resource leak vulnerability that allows authenticated UEs to exhaust the session pool by triggering failed DNN or S-NSSAI validation. Attackers can repeat PDU Session Establishment Requests with different PDU Session Identity values, leaving stale amf_sess contexts that degrade service for other subscribers.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Analysis

by VulDB Data Team • 11/20/2026

The vulnerability identified in Open5GS AMF versions up to 2.8.0 represents a significant resource exhaustion flaw rooted in the handling of session management procedures within the Access and Mobility Management Function. This component is critical for maintaining stateful connections with User Equipment, specifically managing the lifecycle of PDU sessions which define how data flows between the UE and the Data Network. The core technical deficiency lies in the failure to properly release or clean up internal context structures when specific validation checks fail during session establishment attempts. When a UE initiates a connection by sending a PDU Session Establishment Request, the AMF allocates memory resources to create an amf_sess context object intended to track this interaction. However, if the request contains invalid parameters such as an incorrect Data Network Name or S-NSSAI value that fails validation logic before completion, the system does not invoke the necessary cleanup routines to free these allocated contexts. This results in a classic resource leak where memory and session table entries are consumed but never returned to the available pool for reuse by legitimate processes.

From an operational perspective, this flaw allows authenticated attackers to systematically degrade or completely deny service to other subscribers on the network. By repeatedly sending PDU Session Establishment Requests with varying PDU Session Identity values, an attacker can rapidly fill up the session table of the AMF. Since each failed attempt leaves behind a stale context that persists in memory, the cumulative effect is a gradual but steady consumption of finite system resources. Once the session pool is exhausted, new legitimate connection attempts from valid users will fail because there are no available slots to allocate for their sessions. This effectively creates a Denial of Service condition where authorized subscribers cannot establish data connections despite having valid credentials and network access rights. The impact extends beyond simple connectivity loss as it can also lead to increased CPU load due to the continuous processing of these malformed requests, further straining system performance during an active attack scenario.

This vulnerability aligns with CWE-401 which describes a missing release of memory after effective usage leading to resource exhaustion. It is particularly dangerous in 5G core networks because it targets a fundamental control plane function that must remain highly available and responsive at all times. The ability for authenticated users to trigger this condition highlights a gap in input validation hygiene where the system assumes successful completion before committing resources permanently or fails to implement rollback mechanisms upon early termination of procedures due to errors. In terms of threat modeling, this behavior is consistent with ATT&CK technique T1496 which involves resource hijacking through environmental exploitation, specifically targeting computational capacity and memory availability within a network infrastructure component.

Mitigation strategies must focus on ensuring robust state management during error conditions. Developers should audit the code paths associated with DNN and S-NSSAI validation to guarantee that any allocated amf_sess contexts are explicitly freed regardless of whether the session establishment succeeds or fails due to parameter errors. Implementing strict rate limiting for PDU Session Establishment Requests from individual UEs can also help mitigate the speed at which resources are consumed, providing a defensive layer against rapid exhaustion attacks. Additionally, deploying monitoring solutions that track AMF memory usage and active session counts in real time allows operators to detect anomalous patterns indicative of such an attack early enough to take corrective action before service degradation becomes critical for other users.

Responsible

VulnCheck

Reservation

11/20/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00710

KEV

no

Activities

very low

Sources

Do you want to use VulDB in your project?

Use the official API to access entries easily!