Vulnerabilities

Zimbra CVE-2026-73570: over 270 mail servers compromised a month after the fix shipped

Attackers are exploiting a command-injection flaw in Zimbra's SNMP component; Shadowserver counted 274 compromised servers by 22 August, a month after the fix.

All articles

Attackers are breaking into self-hosted Zimbra Collaboration mail servers through CVE-2026-73570, a command-injection flaw in the suite’s optional SNMP monitoring component. Poland’s CERT Polska reported active exploitation on 17 August, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added the bug to its Known Exploited Vulnerabilities (KEV) catalog four days later, and the Shadowserver Foundation counted 274 compromised servers in its scans on 22 August, according to BleepingComputer.

The fix has been available since 20 July, when Zimbra released version 10.1.20. Every server compromised through this flaw was therefore still running an older version, and Shadowserver’s first reported count of compromised servers came on 20 August, a full month after the patch shipped. For organizations that run their own email on Zimbra, the question this week is not only “have we patched?” but also “what happened on this server before we did?”

What happened

According to the CVE record, Zimbra Collaboration (ZCS) versions before 10.1.20 are affected when the optional zimbra-snmp package is installed and SNMP notifications are enabled. Because input is not properly sanitized during SNMP notification processing, an unauthenticated attacker can send specially crafted SMTP requests that result in operating-system commands running as the zimbra user. MITRE, which assigned the CVE, rates it 8.9 (high) on CVSS 3.1, with high attack complexity. CERT Polska specifies that the vulnerable setup involves SNMP traps enabled through the snmp_notify parameter together with the swatchdog monitoring service, which runs by default. Shadowserver describes the affected configuration as non-default and stresses that an unpatched server is not automatically an exploitable one.

The timeline so far:

  • 26 June 2026: Zimbra issues a security advisory on the SNMP vulnerability; a temporary mitigation is available until a permanent fix ships (Help Net Security).
  • 20 July 2026: Zimbra 10.1.20 ships the permanent fix. Zimbra rates the release’s security severity “High” and its deployment risk “Low”.
  • 13 August 2026: CVE-2026-73570 is published.
  • 17 August 2026: CERT Polska warns of an ongoing exploitation campaign and publishes indicators of compromise.
  • 20 August 2026: Shadowserver flags 155 compromised Zimbra instances.
  • 21 August 2026: CISA adds the flaw to KEV; U.S. federal civilian agencies must remediate by 24 August.
  • 22 August 2026: Shadowserver reports 274 instances “seen compromised in our scans for exploitation artifacts” and at least 8,200 instances not yet on 10.1.20.

Neither CERT Polska nor CISA has named who is behind the campaign or published details of the exploit beyond the indicators of compromise. Zimbra flaws have repeatedly drawn both state-sponsored groups and cybercriminals, often to steal sensitive email, as BleepingComputer notes.

Why it matters

A mail server is a master key

An email server holds far more than messages. It stores contracts, invoices and HR correspondence; it receives the password-reset links for most other business systems; and it keeps the account directory and service credentials the platform needs to run. Code execution as the zimbra user, the account that runs the mail services and owns their data, puts all of that within reach. An intruder can read mailboxes, plant forwarding rules, collect credentials, and send convincing fraud emails from a domain that customers and partners already trust.

The trigger comes through the front door

Per the CVE description, the malicious input arrives as SMTP traffic: the protocol every internet-facing mail server must accept from anyone. Blocking SNMP ports at the firewall does not remove the trigger, because the crafted input reaches the vulnerable component through normal mail processing. What closes the path is upgrading, or removing the conditions the flaw depends on.

Patched is not the same as clean

Upgrading to 10.1.20 closes the vulnerability; it does not remove a web shell, a rogue account or credentials stolen earlier. CERT Polska asks administrators to review files created over the previous 30 days, and CISA’s alert notes that its Binding Operational Directive 26-04 sets expectations for when federal agencies must check whether a system was compromised before the patch was applied. The same logic applies to any private company whose server stayed on an older version through July and August.

CVE-driven processes can lag

The fix was listed in Zimbra’s release notes on 20 July, and the vendor had already advised customers about the issue in June. The CVE identifier, however, only appeared on 13 August, and the KEV listing on 21 August. Teams whose patch priorities come from scanners and dashboards keyed to CVE IDs, or that wait for a KEV entry, would have seen little urgency for weeks. For internet-facing systems, the vendor’s own security channel is the earliest reliable signal.

What to do now

  1. Confirm exposure. List every Zimbra server, its exact version, and whether zimbra-snmp is installed and SNMP notifications are enabled. Check the live configuration, not the original build documents. Platforms derived from Zimbra code, such as Zextras Carbonio, follow their own release cycles; check that vendor’s advisories rather than assuming either way.
  2. Upgrade to 10.1.20 or later now. If that cannot happen today, follow Zimbra’s interim guidance and, where SNMP monitoring is not essential, disable SNMP notifications or remove the optional package; the flaw requires both to be present. Servers on older, unsupported branches should be moved to a supported release rather than left waiting.
  3. Hunt for compromise, even on patched servers. Use CERT Polska’s indicators: unusual “Service status change” entries in /var/log/zimbra.log, and files created by the zimbra user in /opt/zimbra/jetty/webapps/, /opt/zimbra/jetty_base/webapps/ and /tmp/. Those web application directories are where a web shell, a small script that gives an attacker remote control through the web server, would typically sit. If you upgraded late, look back to 20 July, not just 30 days.
  4. Treat any hit as an incident. Isolate the server, preserve logs and a disk image before cleaning anything, and rebuild from a known-good state. Rotate every credential the server held: user and admin passwords, service and directory (LDAP) passwords, and keys stored on the host. Review mailbox forwarding rules and filters for unexpected changes.
  5. Shrink the exposed surface. Keep the admin console off the public internet behind a VPN or an IP allow-list, enable multi-factor authentication for webmail and admin access where your edition supports it, and limit SNMP to a management network.
  6. Move logs off the box. Ship mail, proxy and system logs to central storage the mail server cannot alter, keep at least 90 days, and add file-integrity monitoring on web application directories so that a new script raises an alert.
  7. Fix the patch process. Subscribe to Zimbra’s security advisories and blog feed, and set a target of days, not weeks, for high-severity fixes on internet-facing mail systems, whether or not a CVE has been assigned.
  8. Check backups and capacity honestly. Keep tested backups of mailboxes and configuration stored separately from the server. If the team cannot sustain this level of patching and log review, consider managed or hosted email.

Era Artech’s perspective

Running email in-house is a legitimate choice for organizations that want control over their data and costs. This case shows what that choice demands in practice: the fix had been available for a month before Shadowserver’s first reported count of compromised servers. We encourage organizations that self-host mail to plan for upgrades within days and a compromise check after every late patch, or to decide deliberately that a managed service is the better fit.

Sources

  1. Patch Release Update: Zimbra 10.1.20 Zimbra ·
  2. CVE-2026-73570 Detail NIST National Vulnerability Database ·
  3. Aktywnie wykorzystywana podatność w Zimbra Collaboration Suite CERT Polska ·
  4. CISA Adds One Known Exploited Vulnerability to Catalog CISA ·
  5. Hackers breached over 270 Zimbra servers in ongoing attacks BleepingComputer ·
  6. Unpatched Zimbra servers are falling to CVE-2026-73570 attacks Help Net Security ·

This analysis reflects information that was publicly available on its publication date. It is provided for general information only and is not legal or professional advice.

Need help assessing your exposure?

Our team can review your systems against the issues discussed here and help you prioritize fixes.

Talk to our security team