Process crash via unchecked PFCP ReportType dereference
Published Jan 30, 2026 · Updated Jan 30, 2026
NULL pointer dereference in free5GC SMF 4.0 and 4.1.0 allows remote attackers to crash the process via a malformed PFCP request. HandlePfcpSessionReportRequest reads req.ReportType.Dldr without first verifying that the mandatory ReportType IE is present. Exploitation requires PFCP access and a valid session in the deactivated state; the resulting panic terminates the entire SMF process.
Summary
What happened
NULL pointer dereference in free5GC SMF 4.0 and 4.1.0 allows remote attackers to crash the process via a malformed PFCP request. HandlePfcpSessionReportRequest reads req.ReportType.Dldr without first verifying that the mandatory ReportType IE is present. Exploitation requires PFCP access and a valid session in the deactivated state; the resulting panic terminates the entire SMF process.
The record
- CVE
- CVE-2026-1683
- Published
- Jan 30, 2026
- Updated
- Jan 30, 2026
- Vendor
- free5GC
- Product
- SMF
- Classifications
- CWE-404, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 30, 2026CVE publishedPublication date reported by the CVE source.
- Jan 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.0
- Affected versionversion=4.1.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- PFCP SessionReportRequest missing ReportType proof of conceptfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo