CVE-2026-26025: free5GC SMF crash (nil pointer dereference) on PFCP SessionReportRequest when ReportType.USAR=1 and UsageReport omits mandatory URRID sub-IE 
free5GC SMF provides Session Management Function for free5GC, an open-source project for 5th generation (5G) mobile core networks. In versions up to and including 1.4.1, SMF panics and terminates when processing a malformed PFCP SessionReportRequest on the PFCP (UDP/8805) interface. No known upstream fix is available, but some workarounds are available. ACL/firewall the PFCP interface so only trusted UPF IPs can reach SMF (reduce spoofing/abuse surface); drop/inspect malformed PFCP SessionReportRequest messages at the network edge where feasible, and/or add recover() around PFCP handler dispatch to avoid whole-process termination (mitigation only).
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-26025?
CVE-2026-26025 has been assessed as a critical severity vulnerability due to its potential to cause a crash in the free5GC SMF.
How do I fix CVE-2026-26025?
To fix CVE-2026-26025, upgrade free5GC SMF to version 1.4.2 or later.
Which versions of free5GC SMF are affected by CVE-2026-26025?
CVE-2026-26025 affects free5GC SMF versions up to and including 1.4.1.
What specific condition triggers the issue in CVE-2026-26025?
CVE-2026-26025 is triggered when a PFCP SessionReportRequest is received with ReportType.USAR=1 and omits the mandatory URRID sub-IE.
What impact does CVE-2026-26025 have on free5GC SMF?
CVE-2026-26025 can lead to a nil pointer dereference, causing the free5GC SMF to crash.