CVE-2026-5360: Free5GC · Type Confusion
Affects Free5GCSource CVE Database V5
Public exploit available · CVSS 6.3 Medium.
Data as of 30 Oct 2026, 11:52 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:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 2 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Free5GC | Affected
| Fixed in– |
GitHubfree5gc/free5gcpkg:github/free5gc/free5gcOther threats | Affected
| Fixed in– |
CPE configurations (1)
cpe:2.3:a:free5gc:free5gc:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available for this vulnerability, identified by commit 26205eb01705754b7b902ad6c4b613c96c881e29. It is best practice to apply this patch to Free5GC version 4.2.0 to remediate the issue. Since this is not a cloud service, remediation depends on applying the patch to affected deployments.
Description
A vulnerability has been found in Free5GC 4.2.0. The affected element is an unknown function of the component aper. Such manipulation leads to type confusion. The attack may be launched remotely. This attack is characterized by high complexity. The exploitability is described as difficult. The exploit has been disclosed to the public and may be used. The name of the patch is 26205eb01705754b7b902ad6c4b613c96c881e29. It is best practice to apply a patch to resolve this issue.
References
- vuldb.com/vuln/354735 (opens in a new tab)
- vuldb.com/vuln/354735/cti (opens in a new tab)
- vuldb.com/submit/781573 (opens in a new tab)
- github.com/free5gc/free5gc/issues/831 (opens in a new tab)
- github.com/free5gc/aper/pull/11 (opens in a new tab)
- github.com/free5gc/free5gc/issues/831 (opens in a new tab)
- github.com/free5gc/aper/commit/26205eb01705754b7b902ad6c4b613c96c881e29 (opens in a new tab)
- github.com/free5gc/free5gc/ (opens in a new tab)