Cyber Resilience

CVE-2025-65562

Free5Gc 4.1.0

Public PoC
Published
18 December 2025
Modified
07 January 2026
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0052 42th percentile
Risk Priority 58 floored blend · peak EPSS

Summary

CVE-2025-65562 is a high-severity Improper Validation of Array Index (CWE-129) vulnerability in Free5Gc Free5Gc. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 42th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

The free5GC UPF suffers from a lack of bounds checking on the SEID when processing PFCP Session Deletion Requests. An unauthenticated remote attacker can send a request with a very large SEID (e.g., 0xFFFFFFFFFFFFFFFF) that causes an integer conversion/underflow in…

more

LocalNode.DeleteSess() / LocalNode.Sess() when a uint64 SEID is converted to int and used in index arithmetic. This leads to a negative index into n.sess and a Go runtime panic, resulting in a denial of service (UPF crash). The issue has been reproduced on free5GC v4.1.0 with crashes observed in the session lookup/deletion path in internal/pfcp/node.go; other versions may also be affected. No authentication is required.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-32937Same product: Free5Gc Free5Gc
CVE-2025-70121Same product: Free5Gc Free5Gc
CVE-2023-47347Same product: Free5Gc Free5Gc
CVE-2025-60633Same product: Free5Gc Free5Gc
CVE-2025-29632Same product: Free5Gc Free5Gc
CVE-2025-56394Same product: Free5Gc Free5Gc
CVE-2025-70122Same product: Free5Gc Free5Gc
CVE-2025-63679Same product: Free5Gc Free5Gc
CVE-2023-47345Same product: Free5Gc Free5Gc
CVE-2026-5360Same product: Free5Gc Free5Gc

Affected Assets

free5gc
free5gc
4.1.0

Mitigating Controls

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and bounds checking that prevent improper array indexing.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development can detect out-of-bounds array access but does not prevent the weakness by itself.

prevents

Secure development lifecycle mandates input validation and bounds checking that directly prevents improper array indexing.

prevents

Application security requirements include validation of untrusted input used for indexing or addressing memory structures.

prevents

Secure architecture principles encourage defensive coding patterns that reduce index-related vulnerabilities.

prevents

Secure coding standards explicitly require bounds checking and validation of array indices derived from untrusted data.

References