CVE-2025-69248
Buffer Overflow in free5GC AMF Causes Remote 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 | amf | to 1.4.1 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-129 | The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability exists in free5GC's AMF service up to version 1.4.1, where a buffer overflow can occur.
Remote unauthenticated attackers can exploit this by sending a specially crafted NAS Registration Request containing a malformed 5GS Mobile Identity.
This causes the AMF service to crash, resulting in a complete denial of service for the 5G core network.
There is no direct workaround at the application level, and applying the official patch from pull request 43 of the free5gc/nas repository is recommended.
How can this vulnerability impact me? :
This vulnerability can lead to a denial of service condition in the 5G core network by crashing the AMF service.
As a result, all deployments of free5GC using the AMF component may experience service outages or disruptions.
Since the attack can be performed remotely and without authentication, it poses a significant risk to network availability.
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?
The immediate step to mitigate this vulnerability is to apply the official patch provided in pull request 43 of the free5gc/nas repository.
No direct workaround is available at the application level, so patching is the recommended action.