Security

CVE-2026-73570: Zimbra Mail Server Exploitation

2 min read

Summary

Microsoft is tracking active exploitation of CVE-2026-73570, an unauthenticated command injection flaw affecting internet-facing Zimbra mail servers with the optional zimbra-snmp package installed and SNMP notifications enabled. The issue can lead to web shell deployment, privilege escalation, mailbox data theft, and persistent remote access, making immediate patching and configuration review critical for administrators.

Need help with Security?Talk to an Expert

Introduction

Microsoft has disclosed active exploitation of CVE-2026-73570, a critical unauthenticated OS command injection vulnerability in the Zimbra Collaboration Suite SNMP notification path. For organizations running internet-facing Zimbra servers, this matters because attackers can trigger code execution through a specially crafted email, with no authentication or user interaction required.

What’s new

Vulnerability details

  • CVE-2026-73570 affects the Zimbra SNMP notification path.
  • Exploitation is possible when the optional zimbra-snmp package is installed and SNMP notifications are enabled.
  • Attackers can send a crafted SMTP request that injects shell commands into SNMP processing.
  • Successful exploitation runs commands with the privileges of the zimbra service account.

Observed attacker activity

Microsoft observed real-world attacks that included:

  • Deployment of JSP web shells in public application directories
  • Use of reverse shells and remote payload downloads via curl or wget
  • Privilege escalation to gain broader control of the host
  • Persistent access through system services and recurring execution methods
  • Mailbox and authentication data collection
  • Archive creation and data exfiltration from compromised mail servers

Timeline

  • July 20, 2026: Zimbra version 10.1.20 released with the relevant remediation
  • July 28 to August 7, 2026: Microsoft observed pre-disclosure scanning and probing
  • August 13, 2026: Public disclosure of CVE-2026-73570

Why this matters for IT administrators

This is not a theoretical issue. Microsoft telemetry shows attackers used both automated exploitation and hands-on-keyboard activity after compromise. Because the vulnerability can be exploited remotely against exposed mail servers, affected organizations may face rapid compromise, persistence, and access to sensitive mailbox data.

Admins should also note that exploitation was observed across multiple regions and industries, so risk is not limited to a specific sector.

  • Update Zimbra immediately to version 10.1.20 or later.
  • Verify whether zimbra-snmp is installed and whether SNMP notifications are enabled.
  • Review internet-facing Zimbra servers for signs of compromise, including:
    • Unexpected JSP files or web shells
    • Suspicious curl, wget, ping, or nslookup activity
    • Unauthorized systemd services or cron jobs
    • Changes to PAM, sudoers, or file permissions
  • Investigate mailbox access, archive creation, and unusual outbound transfers.
  • Isolate and remediate compromised servers if indicators are found.

Bottom line

Organizations running exposed Zimbra infrastructure should treat CVE-2026-73570 as a high-priority incident response and patching issue. If the vulnerable configuration exists, immediate remediation and threat hunting are strongly advised.

Need help with Security?

Our experts can help you implement and optimize your Microsoft solutions.

Talk to an Expert

Stay updated on Microsoft technologies

CVE-2026-73570Zimbracommand injectionmail server securitythreat intelligence

Related Posts

Security

Microsoft Sentinel Named a 2026 SIEM Leader

Microsoft has been named a Leader in the 2026 Gartner Magic Quadrant for SIEM, highlighting the continued momentum behind Microsoft Sentinel. The announcement also underscores Microsoft's push toward integrated, AI-powered security operations through deep Sentinel integration with the new Integrated Security Operations Center in Microsoft Defender.

Security

Microsoft Perception GA: Agentic Security at Ignite

Microsoft has made Microsoft Perception generally available, introducing an agentic security platform that coordinates red, blue, and green team agents through automated playbooks. Announced at Ignite 2026, the update also expands Defender and Sentinel capabilities to help security teams detect, investigate, and remediate AI-speed threats while keeping administrators in control.

Security

Device Code Phishing Risks for AI Coding Agents

Microsoft warns that device code phishing can be used against AI coding agents such as GitHub Copilot CLI, not just user mailboxes or cloud apps. In a controlled lab, a single approved device code sign-in could enable remote session steering, memory poisoning, synced session exposure, and private repository access depending on account permissions and enabled features.

Security

Microsoft 365 Outage Phishing Campaign Targets Users

Microsoft Threat Intelligence reported a high-volume phishing campaign that impersonates Microsoft 365 service-health notifications to trick users into clicking malicious links. The campaign matters because it uses outage-themed urgency and recipient-specific tracking to target multiple industries, increasing the risk of credential theft and follow-on account compromise.

Security

SCKit ScreenConnect Attack: MSPs Must Hunt Now

Microsoft Threat Intelligence confirmed a campaign abusing ConnectWise ScreenConnect to deploy unauthorized remote-access clients and the SCKit worm on MSP-managed endpoints. The activity can also target technician sessions, making this a high-priority incident for defenders because removing a rogue client alone does not eliminate persistence or invalidate exposed sessions.

Security

AI Agent Supply Chain Attacks Target Coding Tools

Microsoft Security researchers detailed two post-training supply chain attack paths that can backdoor coding and terminal agents: dataset poisoning and model poisoning. The findings matter because compromised agents can misuse tools, execute commands, and access sensitive environments even when prompts appear benign, reinforcing the need for stronger controls around training data, model provenance, and tool permissions.