CVE-2025-69247
Heap-Based Buffer Overflow in free5GC UPF Causes DoS
Publication date: 2026-02-23
Last updated on: 2026-02-25
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| free5gc | go-upf | to 1.2.8 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-122 | A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability exists in free5GC go-upf, the User Plane Function implementation for 5G networks. Versions prior to 1.2.8 have a heap-based buffer overflow issue (CWE-122). This occurs when a remote attacker sends a specially crafted PFCP Session Modification Request containing an invalid SDF Filter length field. This malformed request causes a heap buffer overflow, which can crash the UPF network element.
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to a Denial of Service (DoS) condition by crashing the UPF network element. This results in complete service disruption for all connected User Equipments (UEs). Additionally, it may cause cascading failures affecting the Session Management Function (SMF), potentially impacting broader network operations.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade the free5GC go-upf component to version 1.2.8 or later, as this version contains the fix for the heap-based buffer overflow issue.
Additionally, consider monitoring and restricting PFCP Session Modification Requests to prevent specially crafted packets from reaching the UPF network element.