CVE-2021-35209 json
An issue was discovered in ProxyServlet.java in the /proxy servlet in Zimbra Collaboration Suite 8.8 before 8.8.15 Patch 23 and 9.x before…
published 2021-07-02 5 y ago modified 2026-06-17 4 mo ago also EUVD-2021-21853
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.0%
- EPSS 3.0% chance of exploitation in 30 days, percentile 87%
- public exploits
- 0
- none known
Summary
An issue was discovered in ProxyServlet.java in the /proxy servlet in Zimbra Collaboration Suite 8.8 before 8.8.15 Patch 23 and 9.x before 9.0.0 Patch 16. The value of the X-Host header overwrites the value of the Host header in proxied requests. The value of X-Host header is not checked against the whitelist of hosts Zimbra is allowed to proxy to (the zimbraProxyAllowedDomains setting).
Patch / fix
- zimbra collaboration 8.8.15
Exploit prediction
3.00% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- blog.sonarsource.com https://blog.sonarsource.com/zimbra-webmail-compromise-via-email referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
blog.sonarsource.com
/zimbra-webmail-compromise-via-email
exploit, third-party-advisory
-
wiki.zimbra.com
/wiki/Zimbra_Security_Advisories
vendor-advisory
-
wiki.zimbra.com
/wiki/Security_Center
release-notes, vendor-advisory
-
wiki.zimbra.com
/wiki/Zimbra_Releases/9.0.0/P16
release-notes, vendor-advisory
-
wiki.zimbra.com
/wiki/Zimbra_Releases/8.8.15/P23
release-notes, vendor-advisory
Sources
- CVE List CVE-2021-35209
- NVD CVE-2021-35209
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.