Skip to main content
VulnerabilityPublished

CVE-2026-84161: Ericsson CodeChecker · Data Amplification

Affects Ericsson CodeCheckerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.9 Medium : upgrade to 6.29.3 when convenient.

Data as of 6 Nov 2026, 11:04 UTC

CVSS 3.1 base score
4.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (ERIC)CVSS 3.14.9
Patch
Available – fixed in 6.29.3
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade Ericsson CodeChecker to 6.29.3.

Affected software

ProductAffectedFixed in
EricssonCodeCheckerAffected
  • <6.29.3
Fixed in
  • 6.29.3

AI-suggested

Upgrade CodeChecker to version 6.29.3 or later where this issue is fixed. If upgrading is not immediately possible, ensure that the store.analysis_statistics_dir feature remains disabled (its default state) to prevent exploitation. No additional action is required if the feature is not enabled.

Description

CVE-2026-84161 is a vulnerability in Ericsson CodeChecker versions prior to 6.29.3 where enabling the store.analysis_statistics_dir feature allows authorized users with PRODUCT_STORE permission to submit highly compressed Base64-encoded data that is decompressed without size limits. This can lead to excessive memory and disk usage, potentially exhausting resources and impairing service availability. The feature is disabled by default, and no authorization bypass or path traversal is involved.

References

Community reviews

Loading reviews…