Authenticated remote denial of service through unbounded zlib decompression in storeAnalysisStatistics
- Exploited
- No known exploitation
- Fix
- Fixed in 6.29.3
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 6.29.3.
- Last modified
- 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? →
- 8/100 · provisional
- 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
CodeChecker is affected by a denial-of-service flaw in its storeAnalysisStatistics method, which a remote attacker can reach over the network if they hold a store account with PRODUCT_STORE permission for a product. By sending a highly compressed payload, the attacker can exhaust server memory and disk space and make CodeChecker unavailable, but only when the analysis statistics directory setting is enabled.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
When an operator enables store.analysis_statistics_dir, a network client with PRODUCT_STORE permission for a product can call that product's storeAnalysisStatistics Thrift-over-HTTP method. CodeChecker 6.29.0 decodes the attacker-controlled Base64 string and passes the complete compressed input to one-shot zlib.decompress(). No maximum decompressed size is enforced.
This gives a correctly authorized, non-superuser store account a high-ratio memory and persistent-disk amplification primitive. The complete output is first materialized as a Python bytes object and is then written to the configured statistics directory. A sufficiently scaled payload can exhaust the API worker or host memory and impair CodeChecker availability.
The shipped value of store.analysis_statistics_dir is null, so the affected feature is disabled by default. The primary assessment does not rely on authentication being disabled. There is no authorization bypass and no path traversal in this report.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.9/10CVSS 4.9
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 6.29.3.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Ericsson CodeChecker
fixed in 6.29.3
Evidence 1
- Advisory
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-84161
Is CVE-2026-84161 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
Which versions are affected by CVE-2026-84161?
CodeChecker: before 6.29.3.Source: cve.now feed data
How do I fix CVE-2026-84161?
Upgrade to a fixed version: 6.29.3.Source: cve.now feed data