CVE-2025-65566: n/a
A denial-of-service vulnerability exists in the omec-project UPF (pfcpiface component) in version upf-epc-pfcpiface:2.1.3-dev. When the UPF receives a PFCP Session Report Response that is missing the mandatory Cause Information Element, the session report handler dereferences a nil pointer instead of rejecting the malformed message. This triggers a panic and terminates the UPF process. An attacker who can send PFCP Session Report Response messages to the UPF's N4/PFCP endpoint can exploit this flaw to repeatedly crash the UPF and disrupt user-plane services.
AI Analysis
Technical Summary
CVE-2025-65566 is a denial-of-service vulnerability affecting the User Plane Function (UPF) component pfcpiface of the omec-project, specifically version upf-epc-pfcpiface:2.1.3-dev. The vulnerability arises when the UPF receives a PFCP Session Report Response message that lacks the mandatory Cause Information Element. Instead of properly rejecting this malformed message, the session report handler attempts to dereference a nil pointer, triggering a runtime panic that terminates the UPF process. This results in a crash of the UPF, which is a critical network function responsible for forwarding user data in mobile networks. The attack vector requires an attacker to send crafted PFCP Session Report Response messages to the UPF's N4/PFCP endpoint, which is typically exposed internally within the mobile core network. No privileges or user interaction are required to exploit this vulnerability, making it remotely exploitable with low complexity. The impact is a disruption of user-plane services, causing denial of service to mobile subscribers relying on the affected UPF instance. The vulnerability is classified under CWE-476 (NULL Pointer Dereference), indicating a failure to validate input leading to unsafe memory access. The CVSS v3.1 base score is 7.5 (High), with metrics indicating network attack vector, low attack complexity, no privileges required, no user interaction, unchanged scope, no confidentiality or integrity impact, and high availability impact. No patches or known exploits are currently documented, but the vulnerability poses a significant risk to mobile network availability if exploited.
Potential Impact
For European organizations, particularly telecom operators and mobile network providers deploying the omec-project UPF component, this vulnerability poses a significant risk to network availability. Exploitation can cause repeated crashes of the UPF, disrupting user-plane data forwarding and resulting in service outages for mobile subscribers. This can lead to degraded customer experience, potential regulatory scrutiny, and financial losses due to downtime. The disruption of user-plane services can affect critical communications, including emergency services and enterprise mobile applications. Additionally, the vulnerability could be leveraged as part of a broader attack to degrade network infrastructure resilience. Given the increasing reliance on 5G networks and the adoption of open-source components like omec-project in Europe, the impact could be widespread if not mitigated promptly. The lack of confidentiality or integrity impact limits data breach risks, but availability degradation in telecom infrastructure is critical and can have cascading effects on dependent services.
Mitigation Recommendations
To mitigate CVE-2025-65566, European telecom operators should prioritize the following actions: 1) Apply vendor patches or updates as soon as they become available for the omec-project UPF pfcpiface component to ensure proper validation of PFCP messages. 2) Implement strict input validation and sanity checks on PFCP Session Report Response messages at the N4/PFCP interface to reject malformed or incomplete messages before processing. 3) Employ network segmentation and access controls to restrict which entities can send PFCP messages to the UPF, limiting exposure to untrusted sources. 4) Monitor UPF process stability and logs for signs of crashes or malformed PFCP messages to detect potential exploitation attempts early. 5) Consider deploying redundancy and failover mechanisms for UPF instances to maintain user-plane service continuity in case of crashes. 6) Collaborate with omec-project maintainers and the broader telecom security community to stay informed about patches and best practices. These targeted mitigations go beyond generic advice by focusing on protocol-level validation, network controls, and operational monitoring specific to the omec-project UPF environment.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Netherlands, Sweden, Finland, Poland
CVE-2025-65566: n/a
Description
A denial-of-service vulnerability exists in the omec-project UPF (pfcpiface component) in version upf-epc-pfcpiface:2.1.3-dev. When the UPF receives a PFCP Session Report Response that is missing the mandatory Cause Information Element, the session report handler dereferences a nil pointer instead of rejecting the malformed message. This triggers a panic and terminates the UPF process. An attacker who can send PFCP Session Report Response messages to the UPF's N4/PFCP endpoint can exploit this flaw to repeatedly crash the UPF and disrupt user-plane services.
AI-Powered Analysis
Technical Analysis
CVE-2025-65566 is a denial-of-service vulnerability affecting the User Plane Function (UPF) component pfcpiface of the omec-project, specifically version upf-epc-pfcpiface:2.1.3-dev. The vulnerability arises when the UPF receives a PFCP Session Report Response message that lacks the mandatory Cause Information Element. Instead of properly rejecting this malformed message, the session report handler attempts to dereference a nil pointer, triggering a runtime panic that terminates the UPF process. This results in a crash of the UPF, which is a critical network function responsible for forwarding user data in mobile networks. The attack vector requires an attacker to send crafted PFCP Session Report Response messages to the UPF's N4/PFCP endpoint, which is typically exposed internally within the mobile core network. No privileges or user interaction are required to exploit this vulnerability, making it remotely exploitable with low complexity. The impact is a disruption of user-plane services, causing denial of service to mobile subscribers relying on the affected UPF instance. The vulnerability is classified under CWE-476 (NULL Pointer Dereference), indicating a failure to validate input leading to unsafe memory access. The CVSS v3.1 base score is 7.5 (High), with metrics indicating network attack vector, low attack complexity, no privileges required, no user interaction, unchanged scope, no confidentiality or integrity impact, and high availability impact. No patches or known exploits are currently documented, but the vulnerability poses a significant risk to mobile network availability if exploited.
Potential Impact
For European organizations, particularly telecom operators and mobile network providers deploying the omec-project UPF component, this vulnerability poses a significant risk to network availability. Exploitation can cause repeated crashes of the UPF, disrupting user-plane data forwarding and resulting in service outages for mobile subscribers. This can lead to degraded customer experience, potential regulatory scrutiny, and financial losses due to downtime. The disruption of user-plane services can affect critical communications, including emergency services and enterprise mobile applications. Additionally, the vulnerability could be leveraged as part of a broader attack to degrade network infrastructure resilience. Given the increasing reliance on 5G networks and the adoption of open-source components like omec-project in Europe, the impact could be widespread if not mitigated promptly. The lack of confidentiality or integrity impact limits data breach risks, but availability degradation in telecom infrastructure is critical and can have cascading effects on dependent services.
Mitigation Recommendations
To mitigate CVE-2025-65566, European telecom operators should prioritize the following actions: 1) Apply vendor patches or updates as soon as they become available for the omec-project UPF pfcpiface component to ensure proper validation of PFCP messages. 2) Implement strict input validation and sanity checks on PFCP Session Report Response messages at the N4/PFCP interface to reject malformed or incomplete messages before processing. 3) Employ network segmentation and access controls to restrict which entities can send PFCP messages to the UPF, limiting exposure to untrusted sources. 4) Monitor UPF process stability and logs for signs of crashes or malformed PFCP messages to detect potential exploitation attempts early. 5) Consider deploying redundancy and failover mechanisms for UPF instances to maintain user-plane service continuity in case of crashes. 6) Collaborate with omec-project maintainers and the broader telecom security community to stay informed about patches and best practices. These targeted mitigations go beyond generic advice by focusing on protocol-level validation, network controls, and operational monitoring specific to the omec-project UPF environment.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- mitre
- Date Reserved
- 2025-11-18T00:00:00.000Z
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 694455994eb3efac36a31642
Added to database: 12/18/2025, 7:27:21 PM
Last enriched: 12/25/2025, 7:57:07 PM
Last updated: 2/6/2026, 5:15:51 PM
Views: 75
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-2026-2059: SQL Injection in SourceCodester Medical Center Portal Management System
MediumCVE-2025-13523: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in Mattermost Mattermost Confluence Plugin
HighCVE-2026-2103: CWE-321 in Infor SyteLine ERP
HighCVE-2026-2058: SQL Injection in mathurvishal CloudClassroom-PHP-Project
MediumCVE-2026-25556: CWE-415 Double Free in Artifex Software MuPDF
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
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.