A memory exhaustion issue exists in Open5GS v2.8.0 in the HTTP/2 SBI server.
Affects Open5GS v2.8.0 using its HTTP/2-based SBI server. No fixed version is listed in the checked sources.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: The checked facts contain no workaround or mitigation for this issue.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 12/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Open5GS, an open-source 5G core network software, is affected in its HTTP/2 Service Based Interface server. An unauthenticated remote attacker can send small crafted requests that cause memory to leak and grow until the network function crashes, resulting in denial of service.
Read the original description
A memory exhaustion issue exists in Open5GS v2.8.0 in the HTTP/2 SBI server. Repeated header names cause previously allocated header strings to be leaked, and HPACK compression allows an unauthenticated remote attacker to trigger tens of thousands of duplicate headers with a small request. Repeated crafted requests can cause persistent heap growth, exhaust process memory, and terminate the affected Open5GS network function, resulting in denial of service.
What to do
Workaround: The checked facts contain no workaround or mitigation for this issue.
Timeline
- CVE published
- Record last updated
- First seen by cve.now
Evidence 3
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-106806
What does this mean?
A remote memory exhaustion issue in the HTTP/2 SBI server grows memory use across requests. This terminates the affected Open5GS network function and causes a denial of service.Source: gist.github.com
Am I affected, and how do I check?
The checked sources name Open5GS v2.8.0 with its HTTP/2-based SBI server. Check the installed Open5GS version with your system's package manager or the network function's version output, and check whether the SBI server is configured to use HTTP/2.Source: gist.github.com
What should I do about it?
The checked facts do not name a fixed version or upgrade target.Source: gist.github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What if there's no patch?
The checked facts contain no workaround or mitigation for this issue.Source: gist.github.com