Executive Summary
CVE-2026-76421 is an improper boundary check in the LZX decompression routine used by ClamAV when scanning Microsoft Compiled HTML Help (CHM) files, allowing a crafted CHM file to trigger a buffer overflow and terminate the scanning process. The physical criticality is indirect but real: ClamAV is embedded in file transfer gateways, data diodes, and removable media kiosks that gate content moving into OT zones, and a dead scanner either blocks legitimate operational file transfers or gets bypassed under production pressure.
Technical Exposure Breakdown
The defect sits in the decoder stage of the LZX data algorithm as applied to CHM files. CHM is a container format that uses LZX compression internally. When ClamAV unpacks a CHM to inspect its contents, the decoder fails to validate boundaries correctly, which the source describes as resulting in a buffer overflow. The published attack vector is a crafted CHM file submitted for scanning. No authentication is required, and the attacker does not need a session on the device. They only need their file to reach a ClamAV instance.
The documented impact is denial of service through termination of the scanning process, consistent with the CVSS score of 7.5 in the grounding data. This is not described as remote code execution in the source material, so treat it as an availability problem affecting the inspection control itself rather than a direct code execution path. That distinction matters for prioritization but does not lower the operational concern, because in OT the loss of a security control is often as disruptive as the exploitation of one.
The exploitation condition is low. ClamAV scans files automatically in most deployments. Any ingestion point that accepts arbitrary file uploads, email attachments, or USB content and routes it through ClamAV becomes a trigger surface. An attacker does not need to reach the OT network directly. They need only to land a malicious CHM in a scanning queue that an OT gateway consumes.
OT Impact and Compliance Risk
ClamAV appears far more often in OT and critical infrastructure than most asset owners document. It is bundled into secure file transfer appliances, cross-domain solutions, media sanitization stations required at site entry, and open source gateway stacks that sit at the IT to OT boundary. When the scanner dies, one of two failure modes occurs. In fail-closed configurations, legitimate operational files, firmware updates, HMI configurations, and vendor patches stop moving, which stalls maintenance windows and can delay safety-relevant updates. In fail-open configurations, unscanned content flows into the OT zone, defeating the control entirely.
For IEC 62443, this undermines the conduit controls between zones and the removable media handling requirements that many asset owners rely on for their boundary defense. For NERC CIP, malware prevention and transient cyber asset controls under CIP-007 and CIP-010 depend on functioning scanning at media check stations, and a scanner that can be crashed on demand is a documented gap. For pipeline operators under TSA SD-02C, the segmentation and access control objectives assume inspection controls at the boundary remain available. Water and wastewater utilities operating under AWIA 2018 risk and resilience obligations should treat any boundary inspection failure as a reportable resilience concern.
Compensating Controls
Do not rely on a vendor patch alone. Patch status is unknown in the grounding data, and OT scanning appliances often lag upstream ClamAV releases by months.
- Disable CHM scanning or block CHM files at the ingestion layer if your workflows do not require them. CHM has no legitimate reason to transit most OT file paths.
- Filter CHM by magic bytes at the gateway before the file reaches ClamAV. CHM files begin with the
ITSFsignature. Dropping these upstream removes the trigger entirely. - Deploy a Suricata rule concept that alerts on file transport containing the CHM
ITSFheader across IT to OT conduits, giving visibility into whether crafted files are being staged. - Run ClamAV with process supervision and automatic restart, and alert on repeated scanner termination, which is itself an exploitation indicator.
- Do not active scan OT scanning appliances to confirm the flaw. Probing embedded inspection stacks can crash the very control you depend on.
Note that signature and header filtering is a virtual patch. It reduces the trigger surface but does not fix the underlying decoder defect.
BreachSpider Intel
BreachSpider tracks CVE-2026-76421 and the broader exposure of embedded scanning stacks across industrial boundary devices for monitoring and prioritization.
