VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

codechecker: vulnerability history, versions and safety

codechecker is a package in the PyPI ecosystem. Vulert records 16 vulnerabilities for it across 37 releases, from Jan 2022 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
16 vulnerabilities recorded C3 H1 M4 U8
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
5 in the last 12 months

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all codechecker vulnerabilities

Vulert verdict on codechecker 6.29.1 i

Updated on 23 Oct 2026

Careful: 6.29.1 has 3 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 6.29.1 — affected i
  • Vulnerabilities on record 16 over 4 years · 5 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 10.0 i
  • With no published fix 2 i
  • Depended on by 1 packages i
  • Stars 2,631 i
  • OpenSSF scorecard 5/10 i
  • Last release 1 month ago i
  • Licence Apache-2.0 WITH LLVM-exception i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for codechecker, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
6.29.1 18 Sep 2026 C1 U2 Apache-2.0 WITH LLVM-exception No Details →
6.29.0 09 Sep 2026 C1 U2 Apache-2.0 WITH LLVM-exception No Details →
6.28.3 25 Aug 2026 C1 U2 Apache-2.0 WITH LLVM-exception No Details →
6.28.2 29 Jun 2026 C1 U2 Apache-2.0 WITH LLVM-exception No Details →
6.28.1 17 Jun 2026 C1 U2 Apache-2.0 WITH LLVM-exception No Details →
6.28.0 15 May 2026 C1 U2 Apache-2.0 WITH LLVM-exception No Details →
6.27.3 17 Feb 2026 C1 U1 Apache-2.0 WITH LLVM-exception No Details →
6.27.1 15 Dec 2025 C1 U1 Apache-2.0 WITH LLVM-exception No Details →
6.26.2 22 Sep 2025 C1 U1 Apache-2.0 WITH LLVM-exception No Details →
6.26.1 14 Jul 2025 C1 M1 U2 Apache-2.0 WITH LLVM-exception No Details →
6.26.0 09 Jun 2025 C1 M1 U2 Apache-2.0 WITH LLVM-exception No Details →
6.25.1 20 Mar 2025 C1 M1 U2 Apache-2.0 WITH LLVM-exception No Details →
6.25.0 20 Mar 2025 C1 M1 U2 Apache-2.0 WITH LLVM-exception No Details →
6.24.4 28 Oct 2024 C1 H1 M2 U4 Apache-2.0 WITH LLVM-exception No Details →
6.24.2 18 Oct 2024 C1 H1 M2 U4 Apache-2.0 WITH LLVM-exception No Details →
6.24.1 18 Oct 2024 C3 H1 M2 U6 Apache-2.0 WITH LLVM-exception No Details →
6.24.0 27 Aug 2024 C3 H1 M2 U6 Apache-2.0 WITH LLVM-exception No Details →
6.23.1 14 Dec 2023 C3 H1 M2 U6 Apache-2.0 WITH LLVM-exception No Details →
6.23.0 08 Dec 2023 C3 H1 M2 U6 Apache-2.0 WITH LLVM-exception No Details →
6.23.0rc2 17 Nov 2023 C3 H1 M3 U7 Apache-2.0 WITH LLVM-exception No Details →
6.22.2.post1 30 Oct 2023 C3 H1 M3 U7 Apache-2.0 WITH LLVM-exception No Details →
6.22.2 24 Jul 2023 C3 H1 M3 U7 Apache-2.0 WITH LLVM-exception No Details →
6.22.1 19 Apr 2023 C3 H1 M3 U7 Apache-2.0 WITH LLVM-exception No Details →
6.22.0 14 Apr 2023 C3 H1 M3 U7 Apache-2.0 WITH LLVM-exception No Details →
6.22.0rc1 24 Mar 2023 C3 H1 M3 U7 Apache-2.0 WITH LLVM-exception No Details →
6.21.0 09 Nov 2022 C3 H1 M3 U7 Apache-2.0 WITH LLVM-exception No Details →
6.21.0rc1 27 Oct 2022 C3 H1 M3 U7 Apache-2.0 WITH LLVM-exception No Details →
6.20.0 16 Sep 2022 C3 H1 M3 U7 Apache-2.0 WITH LLVM-exception No Details →
6.20.0rc1 23 Aug 2022 C3 H1 M3 U7 Apache-2.0 WITH LLVM-exception No Details →
6.19.1 18 Mar 2022 C3 H1 M3 U7 Apache-2.0 WITH LLVM-exception No Details →
6.19.0 11 Mar 2022 C3 H1 M3 U7 Apache-2.0 WITH LLVM-exception No Details →
6.18.2 14 Jan 2022 C3 H1 M3 U7 Apache-2.0 WITH LLVM-exception No Details →
6.18.1 10 Dec 2021 C3 H1 M4 U8 Apache-2.0 WITH LLVM-exception No Details →
6.18.0 12 Nov 2021 C3 H1 M4 U8 Apache-2.0 WITH LLVM-exception No Details →
6.17.0 10 Sep 2021 C3 H1 M4 U8 Apache-2.0 WITH LLVM-exception No Details →
6.16.0 04 Jun 2021 C3 H1 M4 U8 non-standard No Details →
6.16.0a1 05 May 2021 C3 H1 M4 U8 non-standard No Details →

All 37 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2024 6
  • 2025 5
  • 2026 4

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 5 of the 16 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for codechecker

The 5 most severe of 16 vulnerabilities recorded for this package

Search all 16 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-10081: CodeChecker Authentication Bypass Vulnerability 10.0 critical 6.24.2 06 Nov 2024
CVE-2026-25660: CodeChecker Authentication Bypass Vulnerability 9.3 critical No fix published 05 May 2026
CVE-2026-25660: CodeChecker Authentication Bypass Vulnerability 9.3 critical No fix published 29 Jun 2026
CVE-2024-10082: CodeChecker Authentication Method Confusion Vulnerability 8.7 critical 6.24.2 06 Nov 2024
CVE-2024-53829: CodeChecker Cross-Site Request Forgery Vulnerability 8.2 high 6.24.5 21 Jan 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About codechecker

Is codechecker safe to use?

Vulert records 16 vulnerabilities for codechecker in PyPI: 3 critical, 1 high, 4 medium and 0 low, plus 8 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is codechecker's Vulert package health score?

Vulert scores codechecker 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of codechecker affected?

Yes. 6.29.1, the version you would install today, has 3 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of codechecker should I use?

6.29.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does codechecker have?

16 vulnerabilities are recorded for codechecker in the PyPI ecosystem: 3 critical, 1 high, 4 medium and 0 low, plus 8 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new codechecker vulnerabilities disclosed?

5 vulnerabilities were recorded for codechecker in the last 12 months, and the oldest entry in this database dates to 21 Jan 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of codechecker are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

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.