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.
CVE-2026-130072
“—” beside the score: it is equal to the CVSS score beside it.
Score 9.1 from GitHub Security Advisory (severity: HIGH) published 2026-11-17. A secondary CVSS source baseline 9.1; sources differ by 0.0.
Also known asEUVD-2026-126721 (ENISA EUVD) · GHSA-jq5x-25v9-fpxq (GitHub Security Advisories)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 9.1
- EG Score
- 9.1CRITICALhigh confidence
- EG Risk
- 72EG Risk 72/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity91% × 45%Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.6%
- EPSS %ILE
- 50th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.
- EG Severity
- 9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 16, 2026
Last Modified
November 18, 2026
Advisory Details (5)
Auto-updated Nov 16, 2026Cloud Commander before 19.21.4 Authentication Bypass and Path Traversal via PUT /rename | Advisories | VulnCheck
https://www.vulncheck.com/advisories/cloud-commander-before-19.21.4-authentication-bypass-and-path-traversal-via-put-renamecloudcmd/server/cloudcmd.js at v19.21.2 · coderaiser/cloudcmd · GitHub
https://github.com/coderaiser/cloudcmd/blob/v19.21.2/server/cloudcmd.js#L253-L258cloudcmd v19.21.4
Patch available: coderaiser/cloudcmd v19.21.4
https://github.com/coderaiser/cloudcmd/releases/tag/v19.21.4commit 25f496ff1c0d (coderaiser/cloudcmd)
Patch available: coderaiser/cloudcmd v19.21.4 (contains commit 25f496ff1c0d)
https://github.com/coderaiser/cloudcmd/commit/25f496ff1c0d512354de92cb7f76c6e86c16aa8fPUT /rename bypasses --auth and escapes --root via arbitrary file move · Issue #486 · coderaiser/cloudcmd · GitHub
https://github.com/coderaiser/cloudcmd/issues/486Vendor Advisories for CVE-2026-130072(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 17× in last 7d / 17× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-22 19:23 UTCGHSA enrichmentGHSA-jq5x-25v9-fpxq · GitHub severity HIGH · GitHub CVSS 9.1
- 2026-11-21 20:33 UTCEchelonGraph re-scored
- 2026-11-21 20:33 UTCGHSA enrichmentGHSA-jq5x-25v9-fpxq · GitHub severity HIGH · GitHub CVSS 9.1
- 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.6% · 50th percentile
- 2026-11-20 21:54 UTCEchelonGraph re-scored
- 2026-11-20 21:54 UTCGHSA enrichmentGHSA-jq5x-25v9-fpxq · GitHub severity HIGH · GitHub CVSS 9.1
- 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-11-19 23:17 UTCEchelonGraph re-scored
- 2026-11-19 23:17 UTCGHSA enrichmentGHSA-jq5x-25v9-fpxq · GitHub severity HIGH · GitHub CVSS 9.1
- 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-11-19 15:20 UTCGHSA enrichmentGHSA-jq5x-25v9-fpxq · GitHub severity HIGH · GitHub CVSS 9.1
- 2026-11-18 16:43 UTCEchelonGraph re-scored
- 2026-11-18 16:43 UTCGHSA enrichmentGHSA-jq5x-25v9-fpxq · GitHub severity HIGH · GitHub CVSS 9.1
- 2026-11-18 16:34 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-11-18 16:28 UTCEchelonGraph re-scored
- 2026-11-18 16:28 UTCGHSA enrichmentGHSA-jq5x-25v9-fpxq · GitHub severity HIGH · GitHub CVSS 9.1
- 2026-11-18 15:48 UTCEchelonGraph re-scored
- 2026-11-18 15:48 UTCGHSA enrichmentGHSA-jq5x-25v9-fpxq · GitHub severity HIGH · GitHub CVSS 9.1
- 2026-11-17 23:24 UTCEchelonGraph re-scored
- 2026-11-17 23:24 UTCGHSA enrichmentGHSA-jq5x-25v9-fpxq · GitHub severity HIGH · GitHub CVSS 9.1
- 2026-11-17 16:34 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-11-17 00:46 UTCEchelonGraph re-scored
- 2026-11-17 00:46 UTCGHSA enrichmentGHSA-jq5x-25v9-fpxq · GitHub severity HIGH · GitHub CVSS 9.1
- 2026-11-16 23:02 UTCENISA EUVD ID recordedEUVD-2026-126721 · Source: ENISA EUVD
- 2026-11-16 22:30 UTCEchelonGraph re-scored
Show 2 moreShow fewer
- 2026-11-16 22:10 UTCEchelonGraph re-scoredFirst assessed: 9.1 CRITICAL
- 2026-11-16 22:04 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-130072?
When was CVE-2026-130072 made public?
Is CVE-2026-130072 actively exploited?
What is the CVSS score of CVE-2026-130072?
How do I remediate CVE-2026-130072?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-130072
Is Your Infrastructure Affected by CVE-2026-130072?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.