CVE-2026-1682: Free5GC SMF · NULL Pointer Dereference
Affects Free5GC SMFSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 54% 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 30 Jan 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 |
|---|---|---|
| Free5GCSMF | Affected
| Fixed in– |
Gogithub.com/free5gc/smfpkg:golang/github.com/free5gc/smfOther threats | Affected
| Fixed in– |
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-1682, organizations should: 1) Monitor Free5GC official repositories and security advisories closely for patches addressing this vulnerability and apply them promptly once released. 2) Implement network-level protections such as firewall rules or PFCP message filtering to restrict or validate PFCP association release requests, limiting exposure to untrusted sources. 3) Deploy anomaly detection systems to identify unusual PFCP traffic patterns indicative of exploitation attempts. 4) Use redundancy and failover mechanisms for SMF instances to minimize service disruption in case of crashes. 5) Conduct regular security assessments and penetration testing focused on PFCP protocol handling to identify similar weaknesses. 6) Limit network exposure of PFCP endpoints by isolating management interfaces and applying strict access controls. 7) Engage with the Free5GC community or vendors for guidance and best practices on secure deployment configurations. These steps go beyond generic advice by focusing on protocol-specific filtering, operational resilience, and proactive monitoring tailored to the 5G core environment.
Description
A flaw has been found in Free5GC SMF up to 4.1.0. Affected is the function HandlePfcpAssociationReleaseRequest of the file internal/pfcp/handler/handler.go of the component PFCP UDP Endpoint. Executing a manipulation can lead to null pointer dereference. The attack may be launched remotely. The exploit has been published and may be used. A patch should be applied to remediate 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/794 (opens in a new tab)
- github.com/free5gc/free5gc/issues/794 (opens in a new tab)
- github.com/free5gc/free5gc/issues/794 (opens in a new tab)
- github.com/free5gc/smf/pull/188 (opens in a new tab)
- github.com/free5gc/smf/ (opens in a new tab)