Vulnerability in Canimaan Software ClamXAV (CVE-2026-105773)
Summary
Vulnerability in Canimaan Software ClamXAV (CVE-2026-105773). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 3.11.1 or later.
Original description
The description as published by the source.
Canimaan Software ClamXAV versions 3.3 - 3.11 contains a local privilege escalation vulnerability in the Privileged Helper Tool caused by a race condition and insufficient file validation, allowing a local attacker to execute arbitrary code with system privileges. Fixed in 3.11.1.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-105773 has been found in Canimaan Software ClamXAV.
Successful exploitation can lead to full system takeover. CVSS score: 7.0/10.
What to do: upgrade Canimaan Software ClamXAV to 3.11.1 or later.
If unsure, ask your IT team or search "Canimaan Software ClamXAV CVE-2026-105773" on the vendor's site.
CVE-2026-105773 (Canimaan Software ClamXAV) — CWE-362 / CVSS v3 7.0
Attack vector: local / no user interaction
Patched: 3.11.1 — 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.
A vulnerability (CWE-362) exists in Canimaan Software ClamXAV.
Check the vendor advisory for the affected versions of Canimaan Software ClamXAV.
Severity: High (CVSS 7.0/10). Successful exploitation can lead to full system takeover.
Update to 3.11.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Canimaan Software ClamXAV を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade Canimaan Software ClamXAV to 3.11.1ステージング環境で 3.11.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web clamxav.com
- web raw.githubusercontent.com
- web cve.org
- web nvd.nist.gov
- web github.com