Azure Linux 3.0 ships ClamAV 1.5.5. Verify the scanner that handles incoming files.

Server rack and metallic file trays illuminated by a blue scanning light.

A file scanner can be a point of failure for an entire mail or upload pipeline. If Azure Linux 3.0 runs ClamAV in that path, check which build is actually scanning the files.

What changed

Microsoft’s November Security Update Guide lists clamav 1.5.4-3 on Azure Linux 3.0 for CVE-2026-76411, CVE-2026-76414, CVE-2026-76415, CVE-2026-76416, CVE-2026-76417, CVE-2026-76421, CVE-2026-76422, CVE-2026-76430, CVE-2026-76515, CVE-2026-76516. Microsoft initially published these entries November 20 UTC and revised them November 21 UTC. The affected rows do not establish the complete older Azure Linux package range.

The ClamAV project released 1.5.5 and 1.4.7 on November 18 to fix these scanning flaws. Microsoft’s production base repository now serves clamav 1.5.5-1.azl3 for x86-64 and ARM64. Both downloads matched the repository checksums, and the files were already hosted November 20. Microsoft still leaves FixedBuild blank in the CVE entries. The package recommendation uses the upstream fix plus the verified Azure Linux RPM. The Microsoft source recipe reviewed still showed 1.5.4-3.

Where it matters

Exposure requires the affected engine to scan matching content, such as email URLs, CHM files, packed executables, Office compound documents or archives. Depending on the flaw and active parser, scanning can crash, stall, or exhaust resources. Microsoft rates the ClamAV rows Important, CVSS 3.1 7.5 except CVE-2026-76415, which it rates Moderate, CVSS 3.1 7.5.

The ten CVEs are absent from the CISA Known Exploited Vulnerabilities catalog as verified November 22. There is no federal KEV deadline. Confirmed exploitation and a vendor-directed compromise check or credential rotation were not verified. Microsoft separately lists libmspack 0.11alpha-2 for CVE-2026-76414 and CVE-2026-76421 with no fixed build supplied. Track separately installed consumers and bundled appliances as their own remediation paths.

MSP action

Suggested priority: High where an affected scanner processes untrusted files. Inventory the OS, RPM, running daemon or library, containers, and mail or upload routes. If scanning is failing, queue or isolate unscanned material where feasible and preserve relevant logs. Pilot the supported repository update, restart or redeploy scanner consumers, then verify the loaded engine, representative scans, queues, resource use and downstream delivery. Preserve scanning coverage during rollout. An Azure Linux host package update does not update a separately bundled scanner.

Official sources

Microsoft November CVRF · ClamAV security release · Microsoft x86-64 repository metadata · Microsoft ARM64 repository metadata · CISA KEV data

Last verified November 22, 2026 ET.

Share this article