VYPR
Moderate severityNVD Advisory· Published Nov 24, 2025· Updated Nov 24, 2025

CVE-2025-60632

CVE-2025-60632

Description

An issue was discovered in Free5GC v4.0.0 and v4.0.1 allowing an attacker to cause a denial of service via crafted POST request to the Npcf_BDTPolicyControl API.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Free5GC v4.0.0 and v4.0.1 are vulnerable to denial of service via a crafted POST request to the Npcf_BDTPolicyControl API due to an unsafe type assertion in the PCF service.

Vulnerability

Overview

An issue discovered in Free5GC versions 4.0.0 and 4.0.1 allows an attacker to cause a denial of service (DoS) by sending a crafted POST request to the Npcf_BDTPolicyControl API [1][1][2]. The root cause is an unsafe type assertion in the PCF (Policy Control Function) service handler. When processing a POST request, the handler attempts to cast the result of deepcopy.Copy(requestMsg) to *models.BdtReqData without verifying whether the copied value is indeed a pointer to that type. If the underlying object is of type `models.BdtReqData (not a pointer), the cast fails and triggers a runtime panic, crashing the PCF service][2].

Exploitation

An attacker can exploit this vulnerability by sending a specially crafted JSON payload to the Npcf_BDTPolicyControl API endpoint. The attack requires network access to the PCF component and, if OAuth is enabled, a valid authorization token for the service][2]. The provided reproduction steps demonstrate that a simple POST request with a JSON body containing fields like aspId, desTimeInt, numOfUes, and volPerUe can trigger the panic. The bug persists in the latest codebase as of the report][2].

Impact

Successful exploitation results in a denial of service condition, causing the PCF service to crash and become unavailable. This disrupts policy control functions within the 5G core network, potentially affecting connected user equipment and services that rely on policy decisions][1][2].

Mitigation

A fix has been proposed in a pull request that addresses the unsafe type assertion by validating the type before casting][3]. Users of Free5GC are advised to apply the patch or update to a version containing the fix once released. Until then, restricting network access to the PCF API and ensuring proper authentication can reduce the attack surface][2][4].

AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected packages

Versions sourced from the GitHub Security Advisory.

PackageAffected versionsPatched versions
github.com/free5gc/pcfGo
< 1.4.01.4.0

Affected products

2
  • Free5GC/Free5GCdescription
  • Free5gc/Free5gcllm-fuzzy
    Range: = 4.0.0, =4.0.1

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

4

News mentions

0

No linked articles in our index yet.