CVE-2025-60633 json
Free5GC is vulnerable to DoS via the Nudm_SubscriberDataManagement API
published 2025-11-24 11 mo ago modified 2026-11-05 4 d ago also GHSA-3j9f-7w24-pcqg , GO-2025-4162 , EUVD-2025-198893
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 32%
- 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 the Nudm_SubscriberDataManagement API.
Patch / fix
- go github.com/free5gc/openapi 1.2.2
- govulncheck-vulndb openSUSE Leap 15.6 0.0.20251230T014957-150000.1.134.1
suse advisories SUSE-SU-2026:0037-1
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
opensuse advisories openSUSE-SU-2026:21483-1
- github.com/free5gc/openapi@d50c83e commit
- github.com/free5gc/udm@57c56a3 commit
- github.com/free5gc/udm@ca99768 commit
- github.com/free5gc/udm@e776c42 commit
- github.com/free5gc/openapi#65 pull request
- github.com/free5gc/udm#63 pull request
- github.com/free5gc/udm#65 pull request
- github.com/free5gc/udm#66 pull request
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 11 mo ago
Exploit prediction
0.38% chance of exploitation in the next 30 days, higher than 32% 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:L/UI:N/S:U/C:N/I:N/A:H |
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/free5gc/udm | <=1.4.0 all versions |
no fix listed |
| go | github.com/free5gc/openapi | <1.2.2 |
1.2.2 |
Classification
- Weakness
-
- CWE-1287 Improper Validation of Specified Type of Input
References
-
github.com
/free5gc/openapi/pull/65
web, patch
-
github.com
/free5gc/udm/pull/63
web, patch
-
github.com
/free5gc/udm/pull/65
web, patch
-
github.com
/free5gc/udm/pull/66
web, patch
-
github.com
/free5gc/openapi/commit/d50c83e8fe7ebf9a62d9de99517e21a17f627b52
web, patch
-
github.com
/free5gc/udm/commit/57c56a3ad4bc53a62cab259045e78ec9abdb98ca
web, patch
-
github.com
/free5gc/udm/commit/ca9976857909a422dcff5bf2228756fc2bfc80d1
web, patch
-
github.com
/free5gc/udm/commit/e776c42177817f75e75e7a587c58c2a027beed81
web, patch
-
github.com
/free5gc/free5gc
product
-
github.com
/free5gc/free5gc/issues/702
web, issue-tracking
-
github.com
/free5gc/free5gc/issues/700
web, issue-tracking
-
github.com
/free5gc/free5gc/issues/701
web, issue-tracking
-
github.com
/free5gc/free5gc/issues/703
web, issue-tracking
-
nvd.nist.gov
/vuln/detail/CVE-2025-60633
advisory
-
github.com
/advisories/GHSA-3j9f-7w24-pcqg
advisory
-
github.com
/free5gc/pcf
package
Sources
- CVE List CVE-2025-60633
- GitHub Advisory GHSA-3j9f-7w24-pcqg
- NVD CVE-2025-60633
- OSV GO-2025-4162
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.