
Advisory and detection guidance for CVE-2026-73570, an unauthenticated OS command injection in Zimbra SNMP notification processing leading to remote code execution.
Zimbra Collaboration Suite Β· SNMP Notification Processing
CVE-2026-73570 is a high-severity OS command injection vulnerability affecting specific configurations of Zimbra Collaboration Suite.
The vulnerability involves the SNMP notification-processing component. Under vulnerable configurations, attacker-controlled data originating from SMTP processing can reach an operating-system command execution context without sufficient input neutralization.
Successful exploitation can result in remote code execution with the privileges of the Zimbra operating-system account.
π΄ Attack Vector: Network π Authentication: None π€ User Interaction: None π» Impact: Remote Code Execution π‘ Attack Surface: SMTP / SNMP notification processing
| Property | Details |
|---|---|
| π CVE | CVE-2026-73570 |
| π’ Product | Zimbra Collaboration Suite |
| π₯ Severity | High |
| π CVSS v3.1 | 8.9 |
| π§© CWE | CWE-78 β OS Command Injection |
| π Attack Vector | Network |
| π Privileges Required | None |
| π€ User Interaction | None |
| π¦ Affected Release | ZCS versions before 10.1.20 under affected configuration |
| β Fixed Release | 10.1.20 |
| π¨ KEV Status | Listed in CISA KEV |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L
π External Attacker β π§ SMTP Processing β βοΈ Zimbra Components β π‘ SNMP Notification Processing β β οΈ Insufficient Input Validation β π» OS Command Injection β π¨ Remote Code Execution
SMTP
β
Zimbra
β
SNMP Notification Processing
β
Untrusted Input
β
OS Command Injection
β
Remote Code Execution
The vulnerable attack path is associated with installations where the relevant SNMP functionality is present and active.
ZCS < 10.1.20
β
βββ zimbra-snmp installed
β
βββ SNMP notifications enabled
β
βββ Notification processing active
Organizations should verify their Zimbra configuration rather than assuming that every installation is vulnerable.
The vulnerability is categorized as:
The security boundary can be represented as:
Untrusted Network Data
β
βΌ
SMTP / Zimbra Processing
β
βΌ
SNMP Notification Path
β
βΌ
Command Construction
β
βΌ
Shell / OS Execution
The fundamental security issue is the failure to adequately neutralize attacker-controlled input before it reaches an operating-system command execution context.
Successful exploitation may allow an attacker to execute commands with the privileges available to the affected Zimbra service account.
Potential consequences include:
The ultimate impact depends on the privileges of the affected service account and the configuration of the surrounding environment.
The primary remediation is to upgrade affected installations to:
Zimbra Collaboration Suite 10.1.20
or a later supported release.
Administrators should determine whether the affected SNMP functionality is required.
Where operationally appropriate:
β’ Review zimbra-snmp installation
β’ Review SNMP notification configuration
β’ Disable unnecessary SNMP notifications
β’ Remove unnecessary components
β’ Apply vendor security guidance
Temporary configuration changes should not replace upgrading to a fixed release.
Security teams should review systems for unusual activity involving:
β’ Unexpected SMTP sources
β’ Abnormally formatted recipient addresses
β’ Suspicious command-like input
β’ Unusual SMTP request patterns
β’ Unexpected notification activity
β’ Abnormal process execution
β’ Unexpected child processes
β’ Suspicious command execution
β’ Unexpected shells
β’ New or modified web-accessible files
β’ Suspicious persistence mechanisms
β’ Unexpected outbound connections
β’ Abnormal processes running as the zimbra user
Monitor for unusual outbound connections originating from Zimbra servers, particularly connections that do not correspond to normal mail-server operations.
CVE-2026-73570 has been added to the CISA Known Exploited Vulnerabilities (KEV) Catalog.
Security organizations have also reported exploitation activity involving vulnerable Zimbra installations.
For internet-facing Zimbra infrastructure, administrators should prioritize:
1. Identify vulnerable installations
2. Verify SNMP configuration
3. Upgrade to a fixed release
4. Review historical logs
5. Hunt for indicators of compromise
6. Investigate unexpected processes and network connections