CVE-2025-60632 json
Free5GC is vulnerable to DoS through its Npcf_BDTPolicyControl POST API
published 2025-11-24 11 mo ago modified 2026-11-05 4 d ago also GHSA-vgq7-9r5r-j9v3 , GO-2025-4164 , EUVD-2025-198894
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 17%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/free5gc/pcf 1.4.0
- govulncheck-vulndb SLE Module for Package Hub 15 SP6, openSUSE Leap 15.6 0.0.20251209T172047-150000.1.127.1
suse advisories SUSE-SU-2025:4395-1
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
opensuse advisories openSUSE-SU-2026:21483-1
- github.com/free5gc/pcf#53 pull request
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 11 mo ago
Exploit prediction
0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/free5gc/pcf | <1.4.0 |
1.4.0 |
Classification
- Weakness
-
- CWE-617 Reachable Assertion
References
-
github.com
/free5gc/pcf/pull/53
web, patch
-
github.com
/free5gc/free5gc
web, product
-
github.com
/free5gc/free5gc/issues/705
web, issue-tracking
-
nvd.nist.gov
/vuln/detail/CVE-2025-60632
advisory
-
github.com
/free5gc/pcf
package
-
github.com
/advisories/GHSA-vgq7-9r5r-j9v3
advisory
Sources
- CVE List CVE-2025-60632
- GitHub Advisory GHSA-vgq7-9r5r-j9v3
- NVD CVE-2025-60632
- OSV GO-2025-4164
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.