Quick answers
- Is CVE-2026-106806 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-106806 being exploited in the wild.
- How severe is CVE-2026-106806?
- Informational severity, published 2 November 2026.
- Which products and versions are affected?
- Open5GS v2.8.0.
- Is there a fix for CVE-2026-106806?
- Yes: fixed in Fixed in commit 76f1537 (referenced fix addressing header leaks and header list size limiting). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-106806 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-106806?
- 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.
How to fix
- Fixed in: Fixed in commit 76f1537 (referenced fix addressing header leaks and header list size limiting)
Technical details
The vulnerability is a memory leak in Open5GS v2.8.0's HTTP/2 SBI server (lib/sbi) where repeated header names cause previously allocated header strings to be leaked without proper deallocation. An unauthenticated remote attacker can exploit HPACK header compression to generate tens of thousands of duplicate headers in a small request; repeated requests cause persistent heap growth that exhausts memory and terminates affected network functions (NRF, SMF, UDM). The fix implemented header reuse, value deallocation on duplicate names, and a 64 KiB limit on decoded request headers.
Affected products
- Open5GS Open5GS v2.8.0
Timeline
- 2026-11-02: disclosed: CVE-2026-106806 published