CVE-2025-60633: free5gc · n/a
Affects free5gcSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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
Weaponised: 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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubfree5gc/free5gcpkg:github/free5gc/free5gcOther threats | 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
1. Restrict network access to the Nudm_SubscriberDataManagement API to trusted and authenticated entities only, using network segmentation and firewall rules. 2. Implement strict access controls and authentication mechanisms to ensure only authorized users with necessary privileges can interact with the vulnerable API. 3. Monitor API usage patterns and logs for abnormal or excessive requests that could indicate exploitation attempts. 4. Deploy intrusion detection and prevention systems (IDS/IPS) tuned to detect anomalous traffic targeting the Nudm API. 5. Engage with Free5GC maintainers and community to track the release of patches or updates addressing this vulnerability and apply them promptly. 6. Conduct regular security assessments and penetration testing focused on 5G core components to identify and remediate similar issues. 7. Prepare incident response plans specifically for 5G core network disruptions to minimize downtime in case of exploitation. 8. Consider deploying redundancy and failover mechanisms for critical 5G core functions to maintain service availability during attacks or failures.
Description
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.