CVE-2026-130072 · Package
NO FIX YET · SEE WHAT TO DO
Cloud Commander (cloudcmd) handles PUT /rename requests before its authentication middleware runs, so anyone can send them. Attackers can use absolute or ../ paths to move any file the Node.js process can read or write, causing data loss or denial of service.
first public Nov 16, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Any deployment of Cloud Commander before 19.21.4 that is reachable from a network the attacker can reach. The sources describe the rename handler running before authentication, so being logged out or having no account does not protect an instance. Teams that do not run cloudcmd can skip it.
Not affected if cloudcmd-not-installed, version-19.21.4-or-later
Who cares cloudcmd, node.js, self-hosted
npm ls cloudcmd in each project or deployment that uses it.unknown as the sources do not say how it is commonly deployed.19.21.4 (fixed version, all versions before this are affected).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.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.