CVE-2025-40843: Ericsson CodeChecker · Stack based buffer overflow
Affects Ericsson CodeCheckerSource CVE Database V5
Not known to be exploited · CVSS 5.9 Medium : upgrade to 6.26.2 when convenient.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.26.2
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-25.
What to do
Upgrade ericsson/codechecker to 6.26.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubericsson/codecheckerpkg:github/ericsson/codecheckerOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Monitor Ericsson’s official channels for the release of patches addressing CVE-2025-40843 and apply updates promptly once available. 2. If you cannot patch yet, restrict access to systems running vulnerable CodeChecker versions, limiting usage of the 'log' command to trusted personnel only. 3. Employ strict local access controls and endpoint security measures to prevent unauthorized local exploitation, including enforcing least privilege principles for developer workstations. 4. Conduct regular integrity checks and monitoring of CodeChecker logs and outputs to detect anomalies that may indicate exploitation attempts. 5. Consider isolating development environments or using containerization to limit the impact of potential exploitation. 6. Educate developers and system administrators about the vulnerability and the importance of cautious handling of CodeChecker tools. 7. Review and enhance internal security policies around software development tools to include vulnerability management and rapid patch deployment. 8. Implement runtime protections such as stack canaries, address space layout randomization (ASLR), and control flow integrity (CFI) where applicable to reduce exploitation success.
Description
CodeChecker is an analyzer tooling, defect database and viewer extension for the Clang Static Analyzer and Clang Tidy. CodeChecker versions up to 6.26.1 contain a buffer overflow vulnerability in the internal ldlogger library, which is executed by the CodeChecker log command. This issue affects CodeChecker: through 6.26.1.