How severe is CVE-2022-41352?

CVE-2022-41352 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-41352?

Affected package information for CVE-2022-41352 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2022-41352?

No fixed version has been published for CVE-2022-41352 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2022-41352 actively exploited in the wild?

Yes. There are 8 known exploit references for CVE-2022-41352, including 6 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-41352?

CVE-2022-41352 has an EPSS (Exploit Prediction Scoring System) score of 94.0%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2022-41352 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2022-41352 (Synacor Zimbra Collaboration Suite (ZCS) Arbitrary File Upload Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-10-20. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-11-10. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2022-41352?

CVE-2022-41352 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2022-41352?

A Nuclei detection template exists for CVE-2022-41352, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2022-41352 published, and has it been updated?

CVE-2022-41352 was published on September 26, 2022 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2022-10-20 — agencies required to remediate by 2022-11-10

CVE-2022-41352

CRITICAL

Published

Sep 26, 2022

Updated

Apr 10, 2026

Affected

0 pkgs

Patched

None yet

Exploits

8 known

EPSS Exploitation Probability

via FIRST.org ↗

94.0%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

An issue was discovered in Zimbra Collaboration (ZCS) 8.8.15 and 9.0. An attacker can upload arbitrary files through amavis via a cpio loophole (extraction to /opt/zimbra/jetty/webapps/zimbra/public) that can lead to incorrect access to any other user accounts. Zimbra recommends pax over cpio. Also, pax is in the prerequisites of Zimbra on Ubuntu; however, pax is no longer part of a default Red Hat installation after RHEL 6 (or CentOS 6). Once pax is installed, amavis automatically prefers it over cpio.

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.