CVE-2026-1976: NULL Pointer Dereference in Free5GC
A weakness has been identified in Free5GC up to 4.1.0. Affected is the function SessionDeletionResponse of the component SMF. This manipulation causes null pointer dereference. The attack is possible to be carried out remotely. The exploit has been made available to the public and could be used for attacks. It is suggested to install a patch to address this issue.
AI Analysis
Technical Summary
CVE-2026-1976 identifies a null pointer dereference vulnerability in Free5GC, an open-source 5G core network implementation widely used by telecom operators and researchers. The flaw resides in the SessionDeletionResponse function within the Session Management Function (SMF) component. When this function processes certain inputs, it fails to properly validate pointers, leading to a null pointer dereference. This condition can cause the SMF process to crash, resulting in denial of service (DoS). The vulnerability is remotely exploitable without requiring authentication or user interaction, making it accessible to unauthenticated attackers over the network. The CVSS 4.0 base score is 6.9 (medium severity), reflecting the ease of exploitation and the impact on service availability. No confidentiality or integrity impact is noted. The vulnerability affects Free5GC versions 4.0 and 4.1.0. Although no active exploitation has been reported in the wild, a public exploit is available, increasing the likelihood of future attacks. Given Free5GC's role as a critical component in 5G core networks, successful exploitation could disrupt mobile network services, affecting subscribers and operators. The lack of a patch link in the provided data suggests that users should monitor official Free5GC repositories and security advisories for updates and apply patches promptly once available.
Potential Impact
The primary impact of CVE-2026-1976 is denial of service against the SMF component of Free5GC, which is a vital part of 5G core network infrastructure. Disruption of SMF services can lead to session management failures, affecting subscriber connectivity and network stability. For telecom operators, this can translate into degraded service quality, dropped connections, and potential revenue loss. The vulnerability does not directly compromise data confidentiality or integrity but undermines network availability, which is critical for 5G services supporting IoT, critical communications, and enterprise applications. The ease of remote exploitation without authentication increases the risk of widespread attacks, especially as 5G networks expand globally. Organizations relying on Free5GC for 5G core functions must consider the operational impact of potential outages and the reputational damage from service interruptions. The availability of a public exploit further elevates the threat landscape, necessitating immediate attention.
Mitigation Recommendations
To mitigate CVE-2026-1976, organizations should: 1) Monitor official Free5GC project repositories and security advisories for the release of patches addressing this vulnerability and apply them promptly. 2) Implement network-level protections such as firewall rules and intrusion detection/prevention systems (IDS/IPS) to restrict access to the SMF component from untrusted networks, limiting exposure to potential attackers. 3) Employ network segmentation to isolate critical 5G core components, reducing the attack surface. 4) Conduct regular security assessments and penetration testing focused on 5G core infrastructure to identify and remediate similar vulnerabilities proactively. 5) Maintain up-to-date incident response plans tailored to telecom network disruptions to minimize downtime in case of exploitation. 6) Consider deploying runtime application self-protection (RASP) or behavior monitoring tools on SMF instances to detect abnormal crashes or exploitation attempts. 7) Engage with the Free5GC community and vendors for timely intelligence sharing and coordinated vulnerability management.
Affected Countries
United States, China, South Korea, Japan, Germany, France, United Kingdom, India, Italy, Canada, Australia, Brazil, Singapore
CVE-2026-1976: NULL Pointer Dereference in Free5GC
Description
A weakness has been identified in Free5GC up to 4.1.0. Affected is the function SessionDeletionResponse of the component SMF. This manipulation causes null pointer dereference. The attack is possible to be carried out remotely. The exploit has been made available to the public and could be used for attacks. It is suggested to install a patch to address this issue.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-1976 identifies a null pointer dereference vulnerability in Free5GC, an open-source 5G core network implementation widely used by telecom operators and researchers. The flaw resides in the SessionDeletionResponse function within the Session Management Function (SMF) component. When this function processes certain inputs, it fails to properly validate pointers, leading to a null pointer dereference. This condition can cause the SMF process to crash, resulting in denial of service (DoS). The vulnerability is remotely exploitable without requiring authentication or user interaction, making it accessible to unauthenticated attackers over the network. The CVSS 4.0 base score is 6.9 (medium severity), reflecting the ease of exploitation and the impact on service availability. No confidentiality or integrity impact is noted. The vulnerability affects Free5GC versions 4.0 and 4.1.0. Although no active exploitation has been reported in the wild, a public exploit is available, increasing the likelihood of future attacks. Given Free5GC's role as a critical component in 5G core networks, successful exploitation could disrupt mobile network services, affecting subscribers and operators. The lack of a patch link in the provided data suggests that users should monitor official Free5GC repositories and security advisories for updates and apply patches promptly once available.
Potential Impact
The primary impact of CVE-2026-1976 is denial of service against the SMF component of Free5GC, which is a vital part of 5G core network infrastructure. Disruption of SMF services can lead to session management failures, affecting subscriber connectivity and network stability. For telecom operators, this can translate into degraded service quality, dropped connections, and potential revenue loss. The vulnerability does not directly compromise data confidentiality or integrity but undermines network availability, which is critical for 5G services supporting IoT, critical communications, and enterprise applications. The ease of remote exploitation without authentication increases the risk of widespread attacks, especially as 5G networks expand globally. Organizations relying on Free5GC for 5G core functions must consider the operational impact of potential outages and the reputational damage from service interruptions. The availability of a public exploit further elevates the threat landscape, necessitating immediate attention.
Mitigation Recommendations
To mitigate CVE-2026-1976, organizations should: 1) Monitor official Free5GC project repositories and security advisories for the release of patches addressing this vulnerability and apply them promptly. 2) Implement network-level protections such as firewall rules and intrusion detection/prevention systems (IDS/IPS) to restrict access to the SMF component from untrusted networks, limiting exposure to potential attackers. 3) Employ network segmentation to isolate critical 5G core components, reducing the attack surface. 4) Conduct regular security assessments and penetration testing focused on 5G core infrastructure to identify and remediate similar vulnerabilities proactively. 5) Maintain up-to-date incident response plans tailored to telecom network disruptions to minimize downtime in case of exploitation. 6) Consider deploying runtime application self-protection (RASP) or behavior monitoring tools on SMF instances to detect abnormal crashes or exploitation attempts. 7) Engage with the Free5GC community and vendors for timely intelligence sharing and coordinated vulnerability management.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulDB
- Date Reserved
- 2026-02-05T13:33:54.329Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 69855cbcf9fa50a62fab62bc
Added to database: 2/6/2026, 3:15:08 AM
Last enriched: 2/23/2026, 10:02:58 PM
Last updated: 3/21/2026, 1:23:15 PM
Views: 56
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.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.