CVE-2026-1976: Free5GC · NULL Pointer Dereference
Affects Free5GCSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 6 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Free5GC | Affected
| Fixed in– |
GitHubfree5gc/free5gcpkg:github/free5gc/free5gcOther threats | Affected
| Fixed in– |
CPE configurations (1)
cpe:2.3:a:free5gc:free5gc:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
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.
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.
References
- vuldb.com (opens in a new tab)
- vuldb.com (opens in a new tab)
- vuldb.com (opens in a new tab)
- github.com/free5gc/free5gc/issues/817 (opens in a new tab)
- github.com/free5gc/free5gc/issues/817 (opens in a new tab)
- github.com/free5gc/smf/pull/189 (opens in a new tab)
- github.com/free5gc/free5gc/ (opens in a new tab)