Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2026-73570: Unauthenticated OS Command Injection in Zimbra Collaboration SNMP Notifications

Published Aug 13, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days13 mentions · peak 4 in a dayToday
CVSS8.9High · v3.1
EPSS76.6%100th percentile
CISA KEVYesAdded Aug 21, 2026
In the wildActivePer CISA KEV
Vendor
Zimbra
IdentifiersCVE-2026-73570CWE-78 · Improper Neutralization of Special…

CVE-2026-73570 is an operating-system command-injection vulnerability in Zimbra Collaboration Suite (ZCS) versions before 10.1.20. It affects installations with the optional zimbra-snmp package installed and SNMP notifications enabled. Crafted SMTP requests place attacker-controlled text into mail-service logs, which swatchdog processes through the SNMP notification pipeline. Insufficient sanitization before shell execution allows injected commands to run with the privileges of the zimbra service account. Exploitation requires neither authentication nor user interaction. The vulnerability is actively exploited.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation compromises the confidentiality and integrity of data and services accessible to the zimbra account and can disrupt mail operations. Observed post-exploitation activity includes JSP web-shell deployment, reverse shells, persistence, theft of service credentials and authentication secrets, mailbox-data collection, and lateral movement between trusted Zimbra cluster nodes. Attackers have also staged mailbox backups for attempted exfiltration. Root access is not an inherent result of this vulnerability; further privilege escalation depends on additional weaknesses or configuration conditions.

Mitigation

If you can’t patch tonight, do this now.

Until patching is possible, disable SNMP notifications or uninstall the optional zimbra-snmp package and stop the associated swatchdog processing. Disabling this functionality reduces SNMP monitoring visibility. Restrict SMTP and SNMP access to trusted hosts where operationally feasible and minimize unnecessary Internet exposure. Monitor for unexpected shell execution originating from Zimbra SNMP processing, unauthorized JSP files, unusual outbound connections, and persistence mechanisms.

Remediation

Patch, then assume compromise.

Upgrade affected Zimbra Collaboration Suite installations to version 10.1.20 or later. Assess previously exposed systems for compromise even if already patched, because the update does not remove established attacker access. Preserve relevant logs and investigate unexpected web shells, processes, services, scheduled tasks, accounts, SSH keys, and changes across mailbox nodes. If compromise is suspected, isolate affected systems and initiate incident response, remove persistence or rebuild systems as appropriate, invalidate affected sessions, and rotate exposed service credentials and Zimbra authentication secrets, including pre-authentication and token-signing keys.

Public exploits

Exploits

6 exploits validated by Mallory's analysis. Hidden: 4 rejected by Mallory's analysis as not a working exploit.

View more in app →
CVE-2026-73570Repository is a small standalone Python proof-of-concept for CVE-2026-73570 affecting Zimbra Collaboration Suite. Structure is minimal: one executable Python script, a README, license, and .gitignore. The main file, CVE-2026-73570.py, implements an unauthenticated web-based command injection attempt against the Zimbra backup extension SNMP trap endpoint. It builds a payload by concatenating the configured SNMP IP with shell metacharacters and an attacker-supplied command, then sends it as the snmp_notify parameter in an HTTPS GET request to /service/extension/backup/snmptrap. The script includes a lightweight pre-check that requests the endpoint and treats any non-404 response as potentially reachable. It disables TLS verification and suppresses certificate warnings, indicating expected use against self-signed admin/web deployments. Success checking is basic: it looks for 'uid=' or HTTP 500 text in the response and otherwise instructs the operator to inspect /var/log/zimbra.log for traces. Capabilities are limited to single-command execution with a hardcoded payload format and default command ('id'), so this is best classified as OPERATIONAL rather than weaponized. README content is mostly generic boilerplate and donation material; it does not add exploit functionality.HORKimhab · Disclosed Aug 21, 2026 · python · markdown · web · networkOperationalCVE-2026-73570Repository contains a single Python exploit script and a README. The main file, CVE-2026-73570.py, is a standalone low-level SMTP client implemented with raw sockets and optional implicit TLS for port 465. Its purpose is to bypass higher-level SMTP library validation and deliver a malformed RCPT TO address containing shell-style command substitution. The exploit flow is: scan common SMTP ports (25/465/587), connect to the selected SMTP service, send EHLO, send a benign MAIL FROM, then send a crafted RCPT TO payload of the form '"x: Service status change: localhost $(command) changed from stopped to running"@cve.invalid'. This is intended to poison server logs with text matching backend monitoring regexes so that a vulnerable downstream component executes the embedded shell command. The code itself does not implement a reverse shell or persistence; it is a command-injection delivery PoC with customizable attacker-supplied shell payloads via --command. The README explains the intended target as vulnerable Zimbra environments and describes the backend conditions required for exploitation: zimbra-snmp installed, snmp_notify enabled, and swatchdog running. It also documents OOB verification using HTTP callbacks (for example, curl to requestrepo.com) and mentions possible post-exploitation access to Zimbra data. Overall, this is a real exploit PoC, not merely a detector: it actively sends exploit traffic over SMTP and supports arbitrary command injection payloads, though payload handling is basic and user-supplied rather than framework-driven.jishino567 · Disclosed Aug 25, 2026 · python · markdown · network · webOperationalCVE-2026-73570The repository contains a README and one Perl executable, zimbra-poc.pl. It is a standalone operational proof-of-concept rather than a Metasploit, Nuclei, or other framework module. The script accepts either a single hostname/IP or a line-oriented target file, supports configurable SMTP port, timeout, direct TLS, verbose session output, and optional local logging. It builds a single payload using the attacker-supplied callback address and reuses it against each selected target. The payload is a base64-obfuscated Bash reverse shell, injected in command substitution within a quoted SMTP RCPT TO local-part. The stated exploit chain is unauthenticated SMTP input reaching /var/log/zimbra.log, swatchdog recognizing a forged `Service status change` pattern, and an unsafe SNMP-notification handler executing attacker-controlled shell content as the zimbra user. The code and documentation indicate exploitation capability, not merely vulnerability detection. No fixed victim hostname, IP address, or callback endpoint is embedded; all network destinations are operator supplied.gabrielunknown · Disclosed Aug 26, 2026 · perl · markdown · networkOperationalCVE-2026-73570The repository contains a single Python 3 executable (`CVE-2026-73570.py`) and a README describing a Zimbra SMTP command-injection PoC for CVE-2026-73570. The visible PoC performs a TCP scan of ports 25, 465, and 587, connects to a chosen SMTP service, issues EHLO and MAIL FROM, and submits a malformed quoted RCPT TO address containing `$(command)` within text designed to match Zimbra swatchdog service-status log patterns. The intended target-side effect is shell command execution if the recipient value reaches an unsafe shell-based swatchdog processing path. The README identifies zimbra-snmp, enabled SNMP notifications, and a running swatchdog process as prerequisites; it says SNMP itself need not be externally exposed. The script is not merely a scanner because it transmits the injection payload, although it has no execution-verification mechanism. Critically, before processing command-line arguments, `main()` invokes an obfuscated `x()` routine. That routine downloads an external script from one of two hardcoded raw.githubusercontent.com URLs, disables certificate validation for the request, writes the data to a temporary file, and executes it silently and detached. This local downloader behavior is unrelated to SMTP testing and makes the repository unsafe to run, as its remote payload can change at any time.byt3l0rd · Disclosed Sep 2, 2026 · python · markdown · network · localOperationalCVE-2026-73570The repository contains a README and a standalone Python 3 proof-of-concept, poc_cve_2026_73570.py, for CVE-2026-73570. It is not tied to an exploit framework and uses only Python standard-library modules (argparse, smtplib, socket, ssl, sys, and time). The script first retrieves an SMTP banner, then submits raw SMTP MAIL FROM and crafted RCPT TO commands. The RCPT local part is designed to resemble a Zimbra 'Service status change' log event while embedding shell injection syntax. If Postfix records the recipient value in /var/log/zimbra.log, the claimed vulnerable zimbra-snmp swatchdog notification workflow matches that text and evaluates it through a shell command. The tool cycles through command-substitution, backtick, semicolon, and IFS-wrapped variants; it supports plaintext SMTP or STARTTLS, configurable target port/hostname, OOB DNS or HTTP callbacks, arbitrary commands, timing delays, transcript debugging, and a non-exploiting SMTP-banner check-only mode. Execution is claimed to occur asynchronously after swatchdog log polling and under the zimbra account rather than root.hainhc · Disclosed Sep 10, 2026 · python · networkOperationalCVE-2026-73570The repository contains a standalone Perl exploit and a Markdown advisory/usage document. CVE-2026-73570.pl is the sole code file and uses IO::Socket::INET and IO::Socket::SSL to connect to one host or a host list over SMTP, with optional direct TLS and configurable timeout, logging, verbosity, target port, and callback address. It constructs a Bash reverse-shell payload using the supplied rhost/rport, Base64-encodes it, and injects it through a crafted quoted SMTP RCPT TO recipient. The intended vulnerability chain is Zimbra SMTP logging of a forged service-status message, swatchdog matching that log text, and an SNMP notification script passing attacker-controlled text to a shell. README.md documents the claimed affected configuration, impact, remediation, and detection guidance. The code is an exploitation tool rather than a scanner: it attempts unauthenticated command execution and a reverse-shell callback, but does not independently verify vulnerability status before delivery.0xBlackash · Disclosed Sep 30, 2026 · perl · markdown · networkOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
ZimbraCollaborationapplication
ZimbraZimbra Collaboration Suiteapplication
FAQ

Frequently asked questions

Is CVE-2026-73570 exploited in the wild?
Yes. As of Nov 20, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Aug 21, 2026.
Is there a public exploit for CVE-2026-73570?
Yes. Mallory tracks 6 public exploits or proofs of concept for CVE-2026-73570, the earliest disclosed Aug 21, 2026.
Is there a patch for CVE-2026-73570?
Upgrade affected Zimbra Collaboration Suite installations to version 10.1.20 or later. Assess previously exposed systems for compromise even if already patched, because the update does not remove established attacker access.
What products are affected by CVE-2026-73570?
Zimbra Collaboration and Zimbra Collaboration Suite.
How severe is CVE-2026-73570?
CVE-2026-73570 has a CVSS v3.1 score of 8.9 (High) and an EPSS score of 76.6% (100th percentile) as of Nov 20, 2026.
Activity feed

Recent activity

335 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
jumpsec labsNews · Nov 3, 2026CartSiphon, a Financially Motivated VShell Cluster | JUMPSECA pre-authentication remote code execution vulnerability in Zimbra Collaboration Suite's SNMP notification processing. CartSiphon's checks73570 tool implements exploitation and webshell deployment, expanding its potential targets beyond e-commerce platforms. The report references exploitation against internet-facing Zimbra servers, but its direct CartSiphon evidence is static analysis rather than an observed successful intrusion.Read more ↗sh3llc0d3 blogNews · Oct 25, 2026Zimbra Collaboration Suite Unauthenticated Remot | ShellcodeThe content describes a critical unauthenticated OS command injection vulnerability in Zimbra's SNMP notification and logging component. Improper sanitization of notification parameters permits command execution as the zimbra user. It reportedly affects ZCS versions before 10.1.20 with SNMP notifications enabled and is being exploited to install JSP web shells, steal directory credentials, and exfiltrate mailboxes. The stated remediation is upgrading to 10.1.20 or later; disabling SNMP notifications or removing zimbra-snmp is offered as an emergency mitigation.Read more ↗infoqNews · Oct 13, 2026ZCS Command Injection via SNMP Handlers Enables Unauthenticated Remote Code Execution - InfoQAn unauthenticated remote command execution vulnerability in Zimbra Collaboration Suite's optional SNMP monitoring subsystem. Attacker-controlled SMTP envelope fields enter logs and are interpolated by swatchdog into an unsanitized shell command, enabling execution as the Zimbra operating system user. The content reports widespread exploitation to install JSP web shells, steal administrative tokens and credentials, and export complete mailboxes. It assigns a CVSS score of 8.9 and reports approximately 274 compromised production instances.Read more ↗security weekNews · Oct 1, 2026Zimbra Vulnerability Exploited in the Wild Prior to Public Disclosure - SecurityWeekA high-severity, unauthenticated remote code execution vulnerability in Zimbra Collaboration Suite SNMP notification processing. Improper sanitization of untrusted input allows specially crafted SMTP requests to execute OS commands as the Zimbra user when the optional zimbra-snmp package is installed and SNMP notifications are enabled.Read more ↗
+12 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence4Every report linking this CVE to a named adversary.
Associated malware19Malware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity183Community discussion across Reddit, Mastodon, and other social sources.