Scanned content reached a logging boundary
ClamAV says CVE-2026-76422 involved Rust-to-C logging. Rendered messages were passed as C format strings instead of data. Crafted input could cause a crash, disclose process memory or corrupt memory when attacker-controlled text reached the logging path.
The project lists ClamAV 0.105.0 through 1.5.4 as affected. The fix is in 1.4.7 and 1.5.5. This is relevant to services that scan content from untrusted users, including mail gateways, upload flows and shared file stores.
Find the scanner behind each workflow
Inventory ClamAV daemons, command-line jobs, containers and products that embed the engine. Trace which services send untrusted files to each scanner and identify whether logs are forwarded to a central system. A fixed host package may not replace an embedded library in a vendor product.
Review crash reports and scanner logs for abnormal events, but do not treat the absence of a message as evidence that the software is patched. Confirm the installed release or supplier build directly.
Update and validate scanning
Install ClamAV 1.4.7 or 1.5.5, or the supported vendor package that contains the fix. Restart long-running scanning processes so they load the updated library. Check that normal files are scanned and that logs remain readable.
Where the scanner runs in containers, rebuild and redeploy the image. Confirm the image digest and scan queue health after rollout.
