free5GC up to 1.4.6 SMF HandlePDUSessionSMContextCreate memory leak
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.7 | $0-$5k | 0.00+ |
Summary
A vulnerability identified as problematic has been detected in free5GC up to 1.4.6. Affected is the function HandlePDUSessionSMContextCreate of the component SMF. Performing a manipulation results in memory leak.
This vulnerability is cataloged as CVE-2026-133700. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in free5GC up to 1.4.6. It has been classified as problematic. This affects the function HandlePDUSessionSMContextCreate of the component SMF. The manipulation with an unknown input leads to a memory leak vulnerability. CWE is classifying the issue as CWE-401. The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse. This is going to have an impact on availability. The summary by CVE is:
free5GC SMF through 1.4.6 contains a resource leak vulnerability in HandlePDUSessionSMContextCreate that leaves SM contexts unreleased when UDM access token retrieval fails. Attackers can trigger repeated PDU session establishment attempts while the NRF is unreachable, causing empty 200 responses and persistent SMF memory growth.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-133700 since 11/20/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
Website
- Product: https://github.com/free5gc/free5gc/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 3.7VulDB Meta Temp Score: 3.7
VulDB Base Score: 4.3
VulDB Temp Score: 4.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 3.1
CNA Vector (VulnCheck): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Memory leakCWE: CWE-401 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
11/20/2026 Advisory disclosed11/20/2026 CVE reserved
11/20/2026 VulDB entry created
11/20/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Not defined
CNA: VulnCheck
CVE: CVE-2026-133700 (🔒)
GCVE (CVE): GCVE-0-2026-133700
GCVE (VulDB): GCVE-100-441429
Entry
Created: 11/20/2026 13:36Changes: 11/20/2026 13:36 (74)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.