CVE Program Container

Answer in brief

CVE-2022-26352 records a High severity vulnerability in CVE Program Container. The current sources mark it as known exploited. The current feed maps n/a/n/a (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Jul 17, 2022Updated Oct 21, 2025Source checked Sep 19, 2026First seen by HOL May 24, 2026Material review Oct 21, 2025

Upstream Advisory

Key facts

Risk: High
Exploitation: Known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

A CVSS score is not reported in the current record. Known-exploitation status makes exposure review time-sensitive. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps n/a/n/a (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
n/a/n/ageneric	n/a	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for n/a/n/a.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Jul 17, 2022
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 21, 2025
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
May 24, 2026
Added to CISA KEV
Aug 25, 2022
Evidence: source:kev:kev:kev:record

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.