CVE-2026-84164: Ericsson CodeChecker · Cross-site Scripting
Affects Ericsson CodeCheckerSource CVE Database V5
Not known to be exploited · CVSS 0.0 High : upgrade to 6.29.3 soon.
Data as of 6 Nov 2026, 11:41 UTC
Thin evidence
One scorer or none| CNA (ERIC) | CVSS 4.0 | 0.0 |
|---|
- Patch
- Available – fixed in 6.29.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 6 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 6 Nov 2026.
What to do
Upgrade Ericsson CodeChecker to 6.29.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| EricssonCodeChecker | Affected
| Fixed in
|
AI-suggested
Upgrade Ericsson CodeChecker to version 6.29.3 or later, where this vulnerability is fixed. If upgrading is not immediately possible, ensure that any environment where the HTML reports are published enforces a restrictive Content Security Policy that blocks inline scripts and mitigates XSS risks. No other specific mitigations are documented.
Description
CVE-2026-84164 is a cross-site scripting (XSS) vulnerability in Ericsson CodeChecker versions before 6.29.3. The vulnerability arises because the HTML reports generated by CodeChecker embed report messages, checker names, and source file paths into a script block using json.dumps, which does not escape the less-than character. This allows a maliciously crafted closing script tag in these fields to break out of the script block and inject arbitrary HTML. The vulnerability affects reports published without a restrictive Content Security Policy (CSP). Jenkins userContent is likely safe due to its restrictive CSP, but other publishing destinations without CSP are vulnerable. The issue is fixed in version 6.29.3.