Back to Intelligence

CVE-2026-130072: Critical Authentication Bypass and Path Traversal in Cloud Commander — Defensive Operations Guide

SA
Security Arsenal Team
November 16, 2026
7 min read

On 06 April 2026, the National Vulnerability Database (NVD) published CVE-2026-130072 with a CVSS v3.1 base score of 9.1 (Critical). The vulnerability affects Cloud Commander (cloudcmd) — a popular web-based file manager for Node.js environments — in all versions prior to 19.21.4.

This flaw combines an authentication bypass with a path traversal condition, allowing unauthenticated attackers to send specially crafted PUT /rename requests that are processed before authentication middleware is applied. By supplying absolute paths or directory traversal sequences (../) in the from and to arrays, an attacker can move any file accessible to the Node.js process outside the configured root directory, leading to data loss, system corruption, or denial of service.

For security teams, this represents a high-risk exposure for any internet-facing or internally accessible Cloud Commander instance. The attack requires no authentication, no user interaction, and is network-exploitable. Immediate inventory, detection, and remediation actions are required.

Technical Analysis

Affected Product and Versions

  • Product: Cloud Commander (cloudcmd)
  • Affected Versions: All versions before 19.21.4
  • Fixed Version: 19.21.4
  • Platform: Any operating system running the affected Node.js package (Windows, Linux, macOS, Docker containers)

Vulnerability Mechanics

Cloud Commander exposes a REST endpoint for file operations. The PUT /rename endpoint accepts a JSON body containing from and to arrays to specify source and destination file paths.

The vulnerability exists because the request handler for /rename is executed before the authentication middleware chain. An unauthenticated attacker can send a request such as:

JSON
{
  "from": ["/etc/passwd"],
  "to":   ["../tmp/pwned"]
}

The application fails to properly normalize and validate that both paths remain within the configured root directory. Because Node.js resolves paths relative to the process working directory or absolute paths directly, the attacker can move sensitive files (configuration files, private keys, database files, logs) to arbitrary locations, overwrite critical system files, or cause denial of service by corrupting application state.

Exploitation Status

At time of publication (06 April 2026), no public proof-of-concept exploit has been widely released, and CVE-2026-130072 has not yet been added to the CISA Known Exploited Vulnerabilities (KEV) catalog. However, the vulnerability is trivially exploitable, network-accessible, and requires no privileges. Organizations should treat this as actively exploitable until proven otherwise. Automated scanners are likely to begin probing for exposed instances within hours to days.

Detection & Response

Because the attack is delivered via HTTP PUT requests to the /rename endpoint, network-level detection is the most reliable control. Endpoint telemetry should focus on suspicious file rename operations performed by the Node.js process and unexpected child process spawning.

Sigma Rules

YAML
---
title: Cloud Commander CVE-2026-130072 - Suspicious Rename Request
id: 550d9a23-0f72-4e3a-a8c5-1d2f3b4c5d6e
status: experimental
description: Detects PUT requests to Cloud Commander /rename endpoint containing path traversal or absolute paths in request body or URI.
references:
  - https://nvd.nist.gov/vuln/detail/CVE-2026-130072
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.initial_access
  - attack.t1190
logsource:
  category: webserver
  product: nodejs
detection:
  selection_uri:
    cs-uri|contains: '/rename'
  selection_method:
    cs-method: 'PUT'
  selection_body:
    cs-body|contains:
      - '../'
      - '/etc/'
      - '/root/'
      - '/bin/'
      - '/sbin/'
      - 'C:\\Windows'
      - 'C:\\Program'
  condition: selection_uri and selection_method and selection_body
falsepositives:
  - Legitimate administrative use of Cloud Commander with unusual paths (rare)
level: high
---
title: Cloud Commander CVE-2026-130072 - Exploitation Attempt via Node.js Process
id: 7a3f1c82-9e4b-4d67-bc12-3e5a8f901234
status: experimental
description: Detects suspicious file rename operations or child process spawning by the Node.js process indicative of CVE-2026-130072 exploitation.
references:
  - https://nvd.nist.gov/vuln/detail/CVE-2026-130072
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.impact
  - attack.t1485
logsource:
  category: process_creation
  product: linux
detection:
  selection_parent:
    ParentImage|endswith: '/node'
  selection_child:
    Image|endswith:
      - '/mv'
      - '/cp'
      - '/rm'
      - '/sh'
      - '/bash'
      - '/python'
  condition: selection_parent and selection_child
falsepositives:
  - Node.js applications that legitimately spawn shell commands (tune to environment)
level: high

KQL — Microsoft Sentinel

KQL — Microsoft Sentinel / Defender
// Hunt for PUT requests to /rename with path traversal patterns (via CommonSecurityLog or WebServer logs)
let suspicious_patterns = dynamic(["../", "/etc/", "/root/", "/bin/", "/sbin/", "C:\\Windows"]);
CommonSecurityLog
| where TimeGenerated > ago(24h)
| where RequestMethod == "PUT"
| where RequestURL contains "/rename"
| extend RequestBody = tostring(AdditionalExtensions)
| where RequestBody has_any (suspicious_patterns) or RequestURL has_any (suspicious_patterns)
| project TimeGenerated, SourceIP, DestinationIP, RequestURL, RequestMethod, RequestBody
| sort by TimeGenerated desc

Velociraptor VQL

VQL — Velociraptor
-- Hunt for Node.js processes performing suspicious file rename operations
SELECT Pid, Ppid, Name, CommandLine, Exe, Username, CreateTime
FROM pslist()
WHERE Name =~ 'node'
   AND (CommandLine =~ 'rename' 
        OR CommandLine =~ '../'
        OR CommandLine =~ '/etc/'
        OR CommandLine =~ '/root/'
        OR CommandLine =~ '/bin/')

Remediation Script (Bash)

Bash / Shell
#!/bin/bash
# CVE-2026-130072 Remediation & Verification Script for Cloud Commander

set -euo pipefail

echo "[+] Checking for installed cloudcmd version..."
if npm list -g cloudcmd >/dev/null 2>&1; then
    INSTALLED_VERSION=$(npm list -g cloudcmd --depth=0 | grep cloudcmd | sed 's/.*@//')
    echo "    Found cloudcmd version: $INSTALLED_VERSION"
    
    if [ "$(printf '%s\n' "19.21.4" "$INSTALLED_VERSION" | sort -V | head -n1)" != "19.21.4" ]; then
        echo "[!] Vulnerable version detected. Updating to 19.21.4..."
        npm update -g cloudcmd
        echo "[+] Update complete. Verify with: npm list -g cloudcmd"
    else
        echo "[+] cloudcmd is already at version $INSTALLED_VERSION (patched)."
    fi
else
    echo "[-] cloudcmd is not installed globally via npm."
fi

echo ""
echo "[+] Checking for running cloudcmd processes..."
pgrep -f "cloudcmd" && echo "[!] cloudcmd is currently running. Consider restarting after patch." || echo "[+] No cloudcmd process detected."

echo ""
echo "[+] Checking for recent suspicious rename activity in logs..."
if [ -f /var/log/nginx/access.log ]; then
    grep -i "PUT.*rename" /var/log/nginx/access.log | grep -E "(\.\./|/etc/|/root/|/bin/)" | tail -20 || echo "    No suspicious PUT /rename requests found in nginx logs."
fi
if [ -f /var/log/apache2/access.log ]; then
    grep -i "PUT.*rename" /var/log/apache2/access.log | grep -E "(\.\./|/etc/|/root/|/bin/)" | tail -20 || echo "    No suspicious PUT /rename requests found in apache logs."
fi

echo ""
echo "[+] Recommendations:"
echo "    1. Update cloudcmd to >= 19.21.4 immediately."
echo "    2. Restrict network access to cloudcmd via firewall or reverse proxy."
echo "    3. Run cloudcmd with least-privilege user and restricted filesystem permissions."
echo "    4. Review file integrity of critical system files if exposure is suspected."

Remediation

  1. Immediate Patch: Upgrade Cloud Commander to version 19.21.4 or later using your package manager (npm update -g cloudcmd, Docker image update, etc.).
  2. Network Segmentation: If immediate patching is not possible, restrict access to Cloud Commander interfaces using firewall rules, VPN, or IP whitelisting. Do not expose cloudcmd directly to the internet.
  3. Principle of Least Privilege: Run the Node.js process under a dedicated low-privilege account. Use chroot, containers, or systemd hardening options (ProtectSystem=strict, ReadOnlyPaths=) to limit filesystem access.
  4. Reverse Proxy Controls: Place Cloud Commander behind a reverse proxy (nginx, Apache, Cloudflare) that enforces authentication, request size limits, and blocks requests containing ../ or absolute paths in the body.
  5. File Integrity Monitoring: Deploy FIM (e.g., AIDE, Tripwire, OSSEC) on critical system and application directories to detect unauthorized file moves.
  6. Log Review: Search historical web server, application, and system logs for PUT /rename requests containing path traversal patterns. Investigate any hits for signs of data theft or corruption.
  7. Container/Image Rebuild: If running in Docker, rebuild containers from updated base images. Remove or patch any cached layers containing vulnerable versions.

Executive Takeaways

  • Act Immediately: CVSS 9.1 + unauthenticated + network-exploitable = patch within 24 hours.
  • Inventory First: Identify all instances of Cloud Commander in your environment, including development, staging, and containerized deployments.
  • Defense in Depth: Patching is primary; network controls and least-privilege execution are essential compensating controls.
  • Monitor for Exploitation: Even after patching, review logs for historical exploitation attempts and deploy the provided detection rules.

Related Resources

Security Arsenal Penetration Testing Services AlertMonitor Platform Book a SOC Assessment vulnerability-management Intel Hub

Is your security operations ready?

Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.