CVE-2025-65564: A denial-of-service vulnerability exists in the omec-upf (upf-epc-pfcpiface) in version upf-epc-pfcpiface:2.1.3-dev…

CVE-2025-65564 · Severity: high · CVSS 7.5 · Published 2025-12-18

A denial-of-service vulnerability exists in the omec-upf (upf-epc-pfcpiface) in version upf-epc-pfcpiface:2.1.3-dev. When the UPF receives a PFCP Association Setup Request that is missing the mandatory Recovery Time Stamp Information Element, the association setup handler dereferences a nil pointer via IE.RecoveryTimeStamp() instead of validating the message. This results in a panic and terminates the UPF process. An attacker who can send PFCP Association Setup Request messages to the UPF's N4/PFCP endpoint can exploit this issue to repeatedly crash the UPF and disrupt user-plane services.

Technologies: Opennetworking Upf. Vendors: Opennetworking.

Quick answers

Is CVE-2025-65564 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-65564 being exploited in the wild.
How severe is CVE-2025-65564?
High severity, with a CVSS score of 7.5, published 18 December 2025.
Which products and versions are affected?
Opennetworking Upf. The advisory does not name versions.
Is there a fix for CVE-2025-65564?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2025-65564?
Check whether you run Opennetworking Upf. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Affected products

  • Opennetworking Upf

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.