Quick answers
- Is CVE-2026-30046 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-30046 being exploited in the wild.
- How severe is CVE-2026-30046?
- High severity, with a CVSS score of 7.5, published 27 August 2026.
- Which products and versions are affected?
- Open5GS v2.7.6.
- Is there a fix for CVE-2026-30046?
- A patch was published: Fix already integrated into Open5GS codebase (status:already-fixed) Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-30046 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-30046?
- 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 is a reachable assertion in the NUDM-UECM (UDM/UECM) interface of Open5GS v2.7.6. When a DELETE request to the SMF registration endpoint omits the required pduSessionId path parameter, the code path reaches an assertion check that fails, causing an immediate process termination (FATAL). The vulnerability is triggered via a network-reachable HTTP/2 DELETE request to the UDM service on the standard NUDM interface. No authentication is required to exploit this DoS condition. The fix has already been applied in the Open5GS codebase (marked as status:already-fixed), indicating a patch is available.
Affected products
- Open5GS Open5GS v2.7.6
Timeline
- 2026-01-08: disclosed: Bug reported on GitHub issue #4264
- 2026-08-27: advisory: NVD advisory published
- patched: Fix already integrated into Open5GS codebase (status:already-fixed)