Skip to main content
VulnerabilityPublished

CVE-2026-109860: CAST Imaging is vulnerable to Path Traversal vulnerability in "/api/server-folders" and

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-109860· High 8.3

Not known to be exploited · CVSS 8.3 High.

Data as of 18 Nov 2026, 17:19 UTC

CVSS 4.0 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (CERT-PL)CVSS 4.08.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
CAST SoftwareImagingAffected
  • =3.6.2
Fixed in–

AI-suggested

The vendor has stated that the vulnerability is fixed in newer versions of CAST Imaging. Users should upgrade to the latest available version to remediate this issue. No additional mitigation guidance or temporary workarounds are provided by the vendor.

Description

CAST Imaging version 3.6.2 is affected by a path traversal vulnerability in the "/api/server-folders" and "/api/server-folders/download" endpoints. These endpoints accept user-supplied filesystem paths and allow execution of certain system commands without sufficient authorization checks. An authenticated attacker can enumerate directories and retrieve arbitrary files outside the intended workspace, such as "/etc/passwd", exposing sensitive data. The vendor has confirmed the issue in version 3.6.2 and stated it is fixed in newer versions, but no specific fixed versions are provided.

References

Community reviews

Loading reviews…