The issue depends on the scan data

CVE-2026-76411 concerns URL canonicalization during ClamAV scans. The release note says an accounting error could write beyond a stack buffer while scanning crafted email when full-hash phishing database entries were loaded. ClamAV lists versions 0.94 through 1.5.4 as affected.

The fix is included in 1.4.7 and 1.5.5. Mail gateways and services that scan email are the first places to check. Other deployments should still confirm whether their scanner processes mail and loads the specified database entries.

Review mail gateway scanner versions

List mail gateways, attachment scanning services, archive pipelines and ClamAV products. Check whether the scanner uses a full-hash phishing database and record how the engine is updated. Include appliances and containers that receive mail before delivery.

Keep the vendor advisory with the asset record. If an appliance vendor packages ClamAV, confirm its fixed release rather than updating the engine outside the supplier’s supported process.

Patch and monitor the mail path

Update to ClamAV 1.4.7 or 1.5.5, or install a supplier build with the correction. Restart the scanning service and send approved test messages through the normal path to confirm delivery and scanning.

Monitor scan errors and mail queue delay after the change. Keep the phishing database update process separate from the engine update so the team can identify which component changed if a scan result differs.