CVE-2025-66720: n/a
CVE-2025-66720 is a null pointer dereference vulnerability found in free5gc PCF version 1. 4. 0, specifically in the HandleDeletePoliciesPolAssoId function within the internal/sbi/processor/ampolicy. go file. This flaw can cause the affected process to crash, potentially leading to denial of service conditions. The vulnerability does not currently have a CVSS score or known exploits in the wild. Exploitation likely requires interaction with the Policy Control Function component of free5gc, a core network function in 5G infrastructure. European organizations deploying free5gc PCF in their 5G networks could experience service disruptions impacting network policy management. Mitigation involves applying patches once available, implementing robust input validation, and monitoring PCF logs for crashes or anomalies. Countries with advanced 5G deployments and open-source 5G core adoption, such as Germany, France, and the UK, are most likely to be affected.
AI Analysis
Technical Summary
CVE-2025-66720 is a software vulnerability identified in the free5gc Policy Control Function (PCF) version 1.4.0, a component of the open-source 5G core network implementation. The vulnerability arises from a null pointer dereference in the function HandleDeletePoliciesPolAssoId, located in the internal/sbi/processor/ampolicy.go source file. A null pointer dereference occurs when the software attempts to access or manipulate memory through a pointer that has not been properly initialized or has been set to null, leading to a runtime error and process crash. In this context, the flaw can cause the PCF process to terminate unexpectedly when handling specific delete policy association requests, resulting in denial of service (DoS) conditions. The PCF is critical in 5G networks as it manages policy rules and charging control, influencing how network resources are allocated and how subscriber sessions are handled. Although no CVSS score has been assigned and no known exploits are reported in the wild, the vulnerability's presence in a core network function means that successful exploitation could disrupt 5G service continuity. The vulnerability was reserved in December 2025 and published in January 2026, indicating recent discovery. The lack of patch links suggests that fixes may not yet be publicly available, emphasizing the need for proactive mitigation. Exploitation likely requires interaction with the PCF's SBI (Service-Based Interface), which may be exposed internally or externally depending on network architecture. This vulnerability highlights the importance of rigorous input validation and error handling in telecom software components to prevent service outages.
Potential Impact
For European organizations operating 5G networks using free5gc PCF 1.4.0, this vulnerability poses a risk of denial of service through crashes of the PCF component. Disruption of the PCF can lead to improper enforcement of network policies, affecting subscriber session management, quality of service, and charging functions. This can degrade user experience, cause service interruptions, and potentially impact revenue. In critical infrastructure or enterprise networks relying on 5G connectivity, such outages could affect operational continuity and safety systems. The impact is heightened in environments where free5gc is deployed in production or testing phases without sufficient isolation or redundancy. Since the vulnerability does not appear to allow remote code execution or privilege escalation, confidentiality and integrity impacts are limited. However, availability is significantly affected due to potential service crashes. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits once details become widely known. European telecom operators and enterprises adopting open-source 5G core solutions should consider this vulnerability in their risk assessments and incident response planning.
Mitigation Recommendations
1. Monitor official free5gc repositories and security advisories for patches addressing CVE-2025-66720 and apply them promptly once available. 2. Implement robust input validation and error handling in the PCF SBI interfaces to prevent null pointer dereferences from malformed or unexpected requests. 3. Deploy redundancy and failover mechanisms for the PCF component to maintain service continuity in case of crashes. 4. Restrict access to the PCF's SBI endpoints using network segmentation, firewalls, and authentication controls to limit exposure to potentially malicious requests. 5. Continuously monitor PCF logs and system metrics for signs of crashes, abnormal terminations, or unusual request patterns that may indicate exploitation attempts. 6. Conduct regular security testing, including fuzzing and code review of the PCF codebase, to identify and remediate similar vulnerabilities proactively. 7. Engage with the free5gc community and vendors to share threat intelligence and coordinate response efforts. 8. Prepare incident response plans specifically addressing potential denial of service scenarios affecting 5G core network functions.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Netherlands, Sweden
CVE-2025-66720: n/a
Description
CVE-2025-66720 is a null pointer dereference vulnerability found in free5gc PCF version 1. 4. 0, specifically in the HandleDeletePoliciesPolAssoId function within the internal/sbi/processor/ampolicy. go file. This flaw can cause the affected process to crash, potentially leading to denial of service conditions. The vulnerability does not currently have a CVSS score or known exploits in the wild. Exploitation likely requires interaction with the Policy Control Function component of free5gc, a core network function in 5G infrastructure. European organizations deploying free5gc PCF in their 5G networks could experience service disruptions impacting network policy management. Mitigation involves applying patches once available, implementing robust input validation, and monitoring PCF logs for crashes or anomalies. Countries with advanced 5G deployments and open-source 5G core adoption, such as Germany, France, and the UK, are most likely to be affected.
AI-Powered Analysis
Technical Analysis
CVE-2025-66720 is a software vulnerability identified in the free5gc Policy Control Function (PCF) version 1.4.0, a component of the open-source 5G core network implementation. The vulnerability arises from a null pointer dereference in the function HandleDeletePoliciesPolAssoId, located in the internal/sbi/processor/ampolicy.go source file. A null pointer dereference occurs when the software attempts to access or manipulate memory through a pointer that has not been properly initialized or has been set to null, leading to a runtime error and process crash. In this context, the flaw can cause the PCF process to terminate unexpectedly when handling specific delete policy association requests, resulting in denial of service (DoS) conditions. The PCF is critical in 5G networks as it manages policy rules and charging control, influencing how network resources are allocated and how subscriber sessions are handled. Although no CVSS score has been assigned and no known exploits are reported in the wild, the vulnerability's presence in a core network function means that successful exploitation could disrupt 5G service continuity. The vulnerability was reserved in December 2025 and published in January 2026, indicating recent discovery. The lack of patch links suggests that fixes may not yet be publicly available, emphasizing the need for proactive mitigation. Exploitation likely requires interaction with the PCF's SBI (Service-Based Interface), which may be exposed internally or externally depending on network architecture. This vulnerability highlights the importance of rigorous input validation and error handling in telecom software components to prevent service outages.
Potential Impact
For European organizations operating 5G networks using free5gc PCF 1.4.0, this vulnerability poses a risk of denial of service through crashes of the PCF component. Disruption of the PCF can lead to improper enforcement of network policies, affecting subscriber session management, quality of service, and charging functions. This can degrade user experience, cause service interruptions, and potentially impact revenue. In critical infrastructure or enterprise networks relying on 5G connectivity, such outages could affect operational continuity and safety systems. The impact is heightened in environments where free5gc is deployed in production or testing phases without sufficient isolation or redundancy. Since the vulnerability does not appear to allow remote code execution or privilege escalation, confidentiality and integrity impacts are limited. However, availability is significantly affected due to potential service crashes. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits once details become widely known. European telecom operators and enterprises adopting open-source 5G core solutions should consider this vulnerability in their risk assessments and incident response planning.
Mitigation Recommendations
1. Monitor official free5gc repositories and security advisories for patches addressing CVE-2025-66720 and apply them promptly once available. 2. Implement robust input validation and error handling in the PCF SBI interfaces to prevent null pointer dereferences from malformed or unexpected requests. 3. Deploy redundancy and failover mechanisms for the PCF component to maintain service continuity in case of crashes. 4. Restrict access to the PCF's SBI endpoints using network segmentation, firewalls, and authentication controls to limit exposure to potentially malicious requests. 5. Continuously monitor PCF logs and system metrics for signs of crashes, abnormal terminations, or unusual request patterns that may indicate exploitation attempts. 6. Conduct regular security testing, including fuzzing and code review of the PCF codebase, to identify and remediate similar vulnerabilities proactively. 7. Engage with the free5gc community and vendors to share threat intelligence and coordinate response efforts. 8. Prepare incident response plans specifically addressing potential denial of service scenarios affecting 5G core network functions.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- mitre
- Date Reserved
- 2025-12-08T00:00:00.000Z
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 697398e14623b1157c4c5d2d
Added to database: 1/23/2026, 3:50:57 PM
Last enriched: 1/23/2026, 4:05:58 PM
Last updated: 1/23/2026, 5:56:02 PM
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-14947: CWE-862 Missing Authorization in plugins360 All-in-One Video Gallery
MediumCVE-2025-31130: CWE-328: Use of Weak Hash in GitoxideLabs gitoxide
MediumCVE-2026-24423: CWE-306 Missing Authentication for Critical Function in SmarterTools SmarterMail
CriticalCVE-2025-29786: CWE-770: Allocation of Resources Without Limits or Throttling in expr-lang expr
HighCVE-2026-1299: CWE-93 in Python Software Foundation CPython
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.