Vulnerability Database · PyPI · codechecker · Version
codechecker 6.26.2
6.26.2 is affected by 3 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 6.29.1.
Critical 2 High 0 Medium 1 Low 0 Unrated 0
-
Released 22 Sep 2025
Licence Apache-2.0 WITH LLVM-exception
Also known from other sources 2
Newer releases 37
Database updated 23/Oct/2026
Release and licence data published by PyPI. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
codechecker 6.26.2 vulnerabilities
3 vulnerabilities cover codechecker 6.26.2. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2026-25660: CodeChecker Authentication Bypass Vulnerability | 9.3 critical | No fix published | 29 Jun 2026 |
| CVE-2026-25660: CodeChecker Authentication Bypass Vulnerability | 9.3 critical | No fix published | 05 May 2026 |
| CVE-2023-49793: CodeChecker - Path Traversal Vulnerability | 6.5 medium | 46bada41e32f3ba0f6011d5c556b579f6dddf07a | 24 Jun 2024 |
Looking for another version, or everything Vulert holds for codechecker?
Questions
About codechecker 6.26.2
Is codechecker 6.26.2 vulnerable?
Yes. 3 vulnerabilities in the Vulert database cover codechecker 6.26.2: 2 critical, 0 high, 1 medium and 0 low. The upgrade Vulert recommends is 6.29.1, and each entry above names the fixed version to move to.
Which version of codechecker should I use instead of 6.26.2?
6.29.1 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 6.26.2 the latest release of codechecker?
No. 6.26.2 was published 22 Sep 2025, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor codechecker for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the codechecker version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.