Digest · Monday

Security digest: July 20, 2026

1 editorial brief and 3 critical advisories.

All digests · RSS · Markdown

Take stock

  • Check exposure: Zimbra CVE-2026-73570: Exploited SNMP Command Injection. Administrators of self-hosted Zimbra Collaboration before 10.1.20, most urgently internet-facing mail servers with zimbra-snmp installed and SNMP notifications enabled.
  • PyPI: 2 critical advisories (lightrag-hku). Check with pip-audit (or: pip show <package>).
  • npm: 1 critical advisory (tar). Check with npm audit (or: npm ls <package>).
  • None of it touches your stack? Then there is nothing to do today. That is a result, not a failure to read carefully.

Editorial briefs

Check exposure

· Vulnerability · CVE-2026-73570

Zimbra CVE-2026-73570: Exploited SNMP Command Injection

If you run Zimbra below 10.1.20, check today whether the optional zimbra-snmp package is installed with SNMP notifications on; if it is, patch and hunt for web shells, because hundreds of such servers have been compromised.

Must act: Administrators of self-hosted Zimbra Collaboration before 10.1.20, most urgently internet-facing mail servers with zimbra-snmp installed and SNMP notifications enabled.

Can relax: Zimbra servers already on 10.1.20 or later, servers without the zimbra-snmp package, and organizations that do not run self-hosted Zimbra.

  1. Check the Zimbra version (su - zimbra -c 'zmcontrol -v') and whether zimbra-snmp is installed (rpm -q zimbra-snmp or dpkg -l zimbra-snmp).
  2. Upgrade every mailbox and MTA node to Zimbra 10.1.20 or later.
  3. If you cannot upgrade yet, uninstall zimbra-snmp or disable SNMP notifications, and restrict SNMP and SMTP access to trusted hosts where you can.

Read the brief →

Known exploited (CISA KEV) 0

Added to CISA’s catalog on this day: confirmed exploitation in the wild. Due date = CISA’s deadline for US federal agencies.

None.

Critical advisories by ecosystem 3

GitHub-reviewed advisories rated critical, published this day (Pacific time).

PyPI 2

Check: pip-audit (or: pip show <package>)

npm 1

Check: npm audit (or: npm ls <package>)