← Back
CVE-2025-40843
Vulnerability in codechecker (CVE-2025-40843)
Summary
vulnerability in codechecker (CVE-2025-40843). Risk of unauthorized operations or information disclosure. Exploitable via ``ldlogger``. Mitigation: upgrade to `6.26.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-40843** has been found in codechecker.
Attackers can target a specific entry point like ``ldlogger`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade codechecker to **6.26.2** or later.
If unsure, ask your IT team or search "codechecker CVE-2025-40843" on the vendor's site.
CVE-2025-40843 (codechecker) — CWE-121 /
Attack vector: local / unauthenticated / no user interaction
Attack surface: `ldlogger`
Patched: `6.26.2` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-121) exists in codechecker. Attackers reach the vulnerable code path via ``ldlogger`` without authentication.
📍 Affected scope
codechecker — . Attack surface: `ldlogger`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **6.26.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'codechecker' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'codechecker' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `codechecker` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade codechecker to 6.26.2ステージング環境で 6.26.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
codechecker
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.26.2"}]}]
pip
codechecker
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.26.2"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-40843
- package https://github.com/Ericsson/codechecker
- web https://github.com/Ericsson/codechecker/security/advisories/GHSA-5xf2-f6ch-6p8r
- web https://github.com/Ericsson/codechecker/commit/4122eb1b43d00c880e4f0747d2ca0a674feb7a50
- web https://github.com/pypa/advisory-database/tree/main/vulns/codechecker/PYSEC-2025-100.yaml
- web https://github.com/advisories/GHSA-5xf2-f6ch-6p8r