Quick answers
- Is CVE-2025-15687 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-15687 being exploited in the wild.
- How severe is CVE-2025-15687?
- Medium severity, with a CVSS score of 4.3, published 12 August 2026.
- Which products and versions are affected?
- Open5GS up to 2.7.6.
- Is there a fix for CVE-2025-15687?
- A patch was published on 2026-08-12: Version 2.7.7 and commit f23d7a5e Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-15687 attacked?
- It is attacked over the network, in an operating system.
- Am I affected by CVE-2025-15687?
- Check whether you run Open5GS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the smf_gx_cca_cb callback function of the SMF Diameter Gx Credit-Control-Answer handler in Open5GS up to version 2.7.6. The flaw involves improper exception handling that fails to gracefully process unexpected or late Diameter messages, leading to assertion failures and denial of service. An attacker can remotely trigger this condition without authentication by sending malformed or out-of-sequence Diameter Gx Credit-Control-Answer messages to the SMF component. The issue was fixed in version 2.7.7 with commit f23d7a5e, which added robust error checks and logging to prevent assertion failures.
Affected products
- Open5GS Open5GS up to 2.7.6
Timeline
- 2026-08-12: disclosed
- 2026-08-12: patched: Version 2.7.7 and commit f23d7a5e