CVE-2025-60632: github.com/free5gc/pcf · Free5GC is vulnerable to DoS through its Npcf_BDTPolicyControl POST API
Affects github.com/free5gc/pcfSource GCVE Database
Not known to be exploited · CVSS 6.5 Medium : upgrade to 1.4.0 when convenient.
Data as of 19 Nov 2026, 02:19 UTC
- Patch
- Available – fixed in 1.4.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 24 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade github.com/free5gc/pcf to 1.4.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Gogithub.com/free5gc/pcf | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Free5GC to version 1.4.0 or later, where this vulnerability is fixed. Since a patch is available, applying the official fix is the recommended mitigation. No additional vendor advisories indicate alternative mitigations or that no action is required.
Description
Free5GC versions prior to 1.4.0 contain a vulnerability in the Npcf_BDTPolicyControl POST API that allows an attacker to cause a denial of service by sending a crafted POST request. This issue affects Free5GC v4.0.0 and v4.0.1 and has been assigned CVE-2025-60632. The vulnerability has a CVSS 3.1 score of 6.5, indicating a medium severity impact focused on availability disruption. A patch is available in version 1.4.0 to address this flaw.