CVE-2025-14955: Improper Initialization in Open5GS
CVE-2025-14955 is a medium-severity vulnerability in Open5GS versions up to 2. 7. 5 involving improper initialization in the PFCP component's ogs_pfcp_handle_create_pdr function. The flaw can be exploited remotely without authentication or user interaction but requires high attack complexity, limiting ease of exploitation. Successful exploitation could lead to limited impact on system availability or integrity. Open5GS is an open-source 5G core network implementation, making this vulnerability relevant to telecom operators and service providers deploying 5G infrastructure. A patch is available and should be applied promptly to mitigate risk. European organizations using Open5GS in their 5G networks are advised to prioritize patching due to the strategic importance of telecom infrastructure. Countries with advanced 5G deployments and open-source adoption are more likely to be affected. The vulnerability does not currently have known exploits in the wild, but public exploit code exists, increasing potential risk if unpatched.
AI Analysis
Technical Summary
CVE-2025-14955 is a vulnerability identified in Open5GS, an open-source 5G core network software, affecting versions 2.7.0 through 2.7.5. The issue resides in the PFCP (Packet Forwarding Control Protocol) component, specifically within the function ogs_pfcp_handle_create_pdr located in lib/pfcp/handler.c. The vulnerability stems from improper initialization during the handling of PFCP Create PDR (Packet Detection Rule) messages. This improper initialization can lead to undefined behavior, potentially causing partial disruption or degradation of the PFCP session management. The vulnerability can be exploited remotely without requiring authentication or user interaction, but the attack complexity is high, indicating that exploitation requires significant expertise or specific conditions. The CVSS v4.0 base score is 6.3 (medium severity), reflecting limited impact on confidentiality, integrity, and availability, and no privileges or user interaction needed. Although no known exploits are currently observed in the wild, exploit code has been publicly disclosed, increasing the risk of future attacks. The patch identified by commit 773117aa5472af26fc9f80e608d3386504c3bdb7 addresses the improper initialization flaw and should be applied to all affected Open5GS deployments to prevent exploitation. Given Open5GS’s role in 5G core network infrastructure, this vulnerability could impact the reliability and security of 5G services if exploited.
Potential Impact
For European organizations, especially telecom operators and network infrastructure providers deploying Open5GS as part of their 5G core networks, this vulnerability poses a risk to the stability and security of critical communications infrastructure. Exploitation could lead to partial disruption or degradation of PFCP session management, potentially affecting data forwarding and session continuity. While the impact on confidentiality and integrity is limited, availability could be affected, leading to service interruptions or degraded network performance. This could have downstream effects on enterprises and consumers relying on 5G connectivity for critical applications. The medium severity and high attack complexity reduce immediate risk, but the public availability of exploit code increases the urgency for patching. European telecom providers operating in competitive and regulated markets must ensure compliance with security standards and protect infrastructure from emerging threats. Failure to patch could also expose organizations to regulatory penalties under frameworks like the NIS Directive and GDPR if service disruptions impact data processing or availability.
Mitigation Recommendations
European organizations should prioritize the following specific mitigation steps: 1) Immediately apply the official patch (commit 773117aa5472af26fc9f80e608d3386504c3bdb7) to all Open5GS instances running versions 2.7.0 through 2.7.5 to remediate the improper initialization vulnerability. 2) Conduct thorough testing in staging environments to ensure patch compatibility with existing network configurations and services. 3) Implement network segmentation and strict access controls to limit exposure of PFCP interfaces to trusted management networks only, reducing the attack surface. 4) Monitor PFCP traffic for anomalous or malformed Create PDR messages that could indicate exploitation attempts. 5) Maintain up-to-date threat intelligence feeds and subscribe to vulnerability advisories related to Open5GS and 5G core components. 6) Develop incident response plans specifically addressing 5G core network threats, including this vulnerability. 7) Engage with vendors and open-source communities for ongoing security updates and best practices. 8) Where possible, deploy additional runtime protections such as memory safety tools or application-layer firewalls to detect and block malformed PFCP messages. These targeted actions go beyond generic patching and help strengthen the overall security posture of 5G core network deployments.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Netherlands, Sweden, Finland, Poland
CVE-2025-14955: Improper Initialization in Open5GS
Description
CVE-2025-14955 is a medium-severity vulnerability in Open5GS versions up to 2. 7. 5 involving improper initialization in the PFCP component's ogs_pfcp_handle_create_pdr function. The flaw can be exploited remotely without authentication or user interaction but requires high attack complexity, limiting ease of exploitation. Successful exploitation could lead to limited impact on system availability or integrity. Open5GS is an open-source 5G core network implementation, making this vulnerability relevant to telecom operators and service providers deploying 5G infrastructure. A patch is available and should be applied promptly to mitigate risk. European organizations using Open5GS in their 5G networks are advised to prioritize patching due to the strategic importance of telecom infrastructure. Countries with advanced 5G deployments and open-source adoption are more likely to be affected. The vulnerability does not currently have known exploits in the wild, but public exploit code exists, increasing potential risk if unpatched.
AI-Powered Analysis
Technical Analysis
CVE-2025-14955 is a vulnerability identified in Open5GS, an open-source 5G core network software, affecting versions 2.7.0 through 2.7.5. The issue resides in the PFCP (Packet Forwarding Control Protocol) component, specifically within the function ogs_pfcp_handle_create_pdr located in lib/pfcp/handler.c. The vulnerability stems from improper initialization during the handling of PFCP Create PDR (Packet Detection Rule) messages. This improper initialization can lead to undefined behavior, potentially causing partial disruption or degradation of the PFCP session management. The vulnerability can be exploited remotely without requiring authentication or user interaction, but the attack complexity is high, indicating that exploitation requires significant expertise or specific conditions. The CVSS v4.0 base score is 6.3 (medium severity), reflecting limited impact on confidentiality, integrity, and availability, and no privileges or user interaction needed. Although no known exploits are currently observed in the wild, exploit code has been publicly disclosed, increasing the risk of future attacks. The patch identified by commit 773117aa5472af26fc9f80e608d3386504c3bdb7 addresses the improper initialization flaw and should be applied to all affected Open5GS deployments to prevent exploitation. Given Open5GS’s role in 5G core network infrastructure, this vulnerability could impact the reliability and security of 5G services if exploited.
Potential Impact
For European organizations, especially telecom operators and network infrastructure providers deploying Open5GS as part of their 5G core networks, this vulnerability poses a risk to the stability and security of critical communications infrastructure. Exploitation could lead to partial disruption or degradation of PFCP session management, potentially affecting data forwarding and session continuity. While the impact on confidentiality and integrity is limited, availability could be affected, leading to service interruptions or degraded network performance. This could have downstream effects on enterprises and consumers relying on 5G connectivity for critical applications. The medium severity and high attack complexity reduce immediate risk, but the public availability of exploit code increases the urgency for patching. European telecom providers operating in competitive and regulated markets must ensure compliance with security standards and protect infrastructure from emerging threats. Failure to patch could also expose organizations to regulatory penalties under frameworks like the NIS Directive and GDPR if service disruptions impact data processing or availability.
Mitigation Recommendations
European organizations should prioritize the following specific mitigation steps: 1) Immediately apply the official patch (commit 773117aa5472af26fc9f80e608d3386504c3bdb7) to all Open5GS instances running versions 2.7.0 through 2.7.5 to remediate the improper initialization vulnerability. 2) Conduct thorough testing in staging environments to ensure patch compatibility with existing network configurations and services. 3) Implement network segmentation and strict access controls to limit exposure of PFCP interfaces to trusted management networks only, reducing the attack surface. 4) Monitor PFCP traffic for anomalous or malformed Create PDR messages that could indicate exploitation attempts. 5) Maintain up-to-date threat intelligence feeds and subscribe to vulnerability advisories related to Open5GS and 5G core components. 6) Develop incident response plans specifically addressing 5G core network threats, including this vulnerability. 7) Engage with vendors and open-source communities for ongoing security updates and best practices. 8) Where possible, deploy additional runtime protections such as memory safety tools or application-layer firewalls to detect and block malformed PFCP messages. These targeted actions go beyond generic patching and help strengthen the overall security posture of 5G core network deployments.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulDB
- Date Reserved
- 2025-12-19T08:31:39.061Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 69458084f063e4fadff5e830
Added to database: 12/19/2025, 4:42:44 PM
Last enriched: 12/19/2025, 4:50:32 PM
Last updated: 12/19/2025, 5:49:59 PM
Views: 4
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-14958: Heap-based Buffer Overflow in floooh sokol
MediumCVE-2025-68478: CWE-73: External Control of File Name or Path in langflow-ai langflow
HighCVE-2025-68430: CWE-24: Path Traversal: '../filedir' in cvat-ai cvat
MediumCVE-2025-63665: n/a
HighCVE-2025-14957: NULL Pointer Dereference in WebAssembly Binaryen
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.