Skip to content
High-Risk Path Traversal Vulnerability in Cloud Commander Disclosed

High-Risk Path Traversal Vulnerability in Cloud Commander Disclosed

First seen 15 Oct 2026, 01:38 UTC • •
API

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •October 15, 2026 at 01:39 UTC
  • •CVE-2026-110690 allows arbitrary file read via path traversal in Cloud Commander.
  • •Affected versions are 19.20.2 through 19.21.1; prior versions are not vulnerable.
  • •Remediation includes urgent patching and restricting access to the vulnerable endpoint.

A path traversal vulnerability identified as CVE-2026-110690 affects Cloud Commander (cloudcmd) versions 19.20.2 to 19.21.1. This flaw allows unauthenticated attackers to exploit the GET /api/v1/pack endpoint, enabling them to read arbitrary files outside the configured root directory, including sensitive files like /etc/passwd. The vulnerability is rated as high risk due to the potential exposure of credentials and sensitive data. Attackers can send crafted traversal paths without needing user authentication. The flaw was published on October 14, 2026, and while it is not confirmed to be, remediation is urgently recommended. Users are advised to upgrade to the fixed release or restrict access to the vulnerable endpoint until patched.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated just now How this analysis works

Timeline

2026-10-14
CVE-2026-110690 published
Cloud Commander vulnerability disclosed, allowing path traversal and arbitrary file read.
Redpacketsecurity

More articles in this cluster (4)

Following this threat?

Track CVE-2026-110690 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Extracted Entities (3)

1 / 3

Common questions

What versions of Cloud Commander are affected?
Cloud Commander versions 19.20.2 through 19.21.1 are affected by this vulnerability.
What should I do if I am using an affected version?
Upgrade to the vendor's fixed release immediately or restrict access to the vulnerable endpoint.
Is there any active exploitation of this vulnerability?
Currently, there is no confirmed active exploitation reported for this vulnerability.