Quick answers
- Is CVE-2026-30045 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-30045 being exploited in the wild.
- How severe is CVE-2026-30045?
- 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-30045?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-30045 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-30045?
- 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 an integer overflow in the /nnrf-disc/v1/nf-instances endpoint's parameter parsing logic, specifically in the `ogs_uint64_from_string()` function (in ogs-conv.c:241). When parsing the requester-features parameter, the code attempts to convert a very large numeric string (e.g., "ffffffffffffffffffffffffffffffffffffffff") to a 64-bit unsigned integer without validating bounds, causing `strtoll()` to fail with a numerical result out of range error. The application then triggers a fatal assertion that crashes the NRF process. The vulnerability is reachable remotely via unauthenticated HTTP/2 GET requests and requires no special preconditions. An attacker can achieve denial of service by repeatedly sending malicious requests to crash the NRF, disrupting 5G core network operations.
Affected products
- Open5GS Open5GS v2.7.6
Timeline
- 2026-08-27: disclosed: Vulnerability advisory published
- 2026-01-08: other: Vulnerability reported in GitHub issue #4263