CVE-2025-63679: free5gc · n/a
Affects free5gcSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 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. Immediate monitoring of NGAP traffic to detect anomalous or malformed UplinkRANConfigurationTransfer messages using deep packet inspection or protocol-aware IDS/IPS systems. 2. Implement network segmentation to isolate the AMF and other core network functions from untrusted networks and limit exposure to potentially malicious gNBs. 3. Apply strict input validation and rate limiting on NGAP messages at the network edge or within the AMF if possible. 4. Engage with free5gc maintainers and security communities to obtain patches or security updates as soon as they become available. 5. Conduct thorough code audits and fuzz testing on NGAP message handling components to identify and remediate similar vulnerabilities proactively. 6. Develop incident response plans specifically for 5G core network disruptions, including fallback procedures and rapid recovery mechanisms. 7. Consider deploying additional security controls such as runtime application self-protection (RASP) or memory protection techniques to mitigate buffer overflow exploitation. 8. Collaborate with telecom vendors and regulators to share threat intelligence and coordinate defensive measures.
Description
free5gc v4.1.0 and before is vulnerable to Buffer Overflow. When AMF receives an UplinkRANConfigurationTransfer NGAP message from a gNB, the AMF process crashes.