Service interruption via missing PFCP Cause validation
Published Dec 18, 2025 · Updated Dec 18, 2025
Denial of service in omec-project UPF pfcpiface 2.1.3-dev allows remote attackers to crash the process via a malformed PFCP response. The handleSessionReportResponse handler reads srres.Cause.Payload[0] without checking whether the mandatory Cause IE exists. Sending a Session Report Response to the N4/PFCP endpoint is sufficient to panic the UPF and interrupt user-plane services.
Summary
What happened
Denial of service in omec-project UPF pfcpiface 2.1.3-dev allows remote attackers to crash the process via a malformed PFCP response. The handleSessionReportResponse handler reads srres.Cause.Payload[0] without checking whether the mandatory Cause IE exists. Sending a Session Report Response to the N4/PFCP endpoint is sufficient to panic the UPF and interrupt user-plane services.
The record
- CVE
- CVE-2025-65566
- Published
- Dec 18, 2025
- Updated
- Dec 18, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 18, 2025CVE publishedPublication date reported by the CVE source.
- Dec 18, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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 Session Report Response missing Cause PoCfunctional · 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