CVE-2024-40129: open5gs · n/a
Affects open5gsSource CVE Database V5
Not known to be exploited · CVSS 8.6 High.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% 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:L/I:L/A:HExploitation evidence
Disclosed: evidence found.
CVE published 16 Jul 2024
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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubopen5gs/open5gspkg:github/open5gs/open5gsOther 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
To mitigate CVE-2024-40129, organizations should immediately assess their Open5GS deployments and apply any available patches or updates from the Open5GS project once released. In the absence of official patches, applying temporary mitigations such as disabling or restricting access to PFCP interfaces from untrusted networks can reduce exposure. Network segmentation and strict firewall rules should be enforced to limit access to 5G core network components. Conduct thorough code reviews and implement secure coding practices to prevent buffer overflows, including bounds checking and use of safe memory handling functions. Employ runtime protections such as Address Space Layout Randomization (ASLR), stack canaries, and memory protection mechanisms to reduce exploitation success. Regular vulnerability scanning and penetration testing focused on 5G core components can help identify and remediate similar issues proactively. Monitoring network traffic for anomalous PFCP messages and establishing incident response plans for 5G infrastructure are also recommended. Collaboration with vendors and security communities to share threat intelligence will enhance preparedness.
Description
Open5GS v2.6.4 is vulnerable to Buffer Overflow.via /lib/pfcp/context.c.