How severe is CVE-2022-26352?

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

Which packages are affected by CVE-2022-26352?

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

How do I fix CVE-2022-26352?

No fixed version has been published for CVE-2022-26352 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-26352 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2022-26352, including 3 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-26352?

CVE-2022-26352 has an EPSS (Exploit Prediction Scoring System) score of 94.3%, 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-26352 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2022-26352 (dotCMS Unrestricted Upload of File Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-08-25. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-09-15. The required action was: Apply updates per vendor instructions. This CVE has been used in known ransomware campaigns. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

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

A Nuclei detection template exists for CVE-2022-26352, 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-26352 published, and has it been updated?

CVE-2022-26352 was published on July 17, 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-08-25 — agencies required to remediate by 2022-09-15 · Ransomware

CVE-2022-26352

CRITICAL

Published

Jul 17, 2022

Updated

Apr 10, 2026

Affected

0 pkgs

Patched

None yet

Exploits

3 known

EPSS Exploitation Probability

via FIRST.org ↗

94.3%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 the ContentResource API in dotCMS 3.0 through 22.02. Attackers can craft a multipart form request to post a file whose filename is not initially sanitized. This allows directory traversal, in which the file is saved outside of the intended storage location. If anonymous content creation is enabled, this allows an unauthenticated attacker to upload an executable file, such as a .jsp file, that can lead to remote code execution.

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.

An issue was discovered in the ContentResource API in dotCMS 3.0 through…

github.comMetasploitJun 2022

An issue was discovered in the ContentResource API in dotCMS 3.0 through…

packetstormsecurity.comNVDJul 2022

An issue was discovered in the ContentResource API in dotCMS 3.0 through…

cisa.govCISAAug 2022

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-26352 in your stack?

O3 detects CVE-2022-26352 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works