Multiple authenticated OS command injection vulnerabilities exist in the Cohesity (formerly Stone Ram) TranZman 4.0 Build 14614 through TZM_1757588060_SEP2025_FULL.depot web application API endpoints (including Scheduler and Actions pages). The appliance directly concatenates user-controlled parameters into system commands without sufficient sanitisation, allowing an authenticated admin user to inject and execute arbitrary OS commands with root privileges. An attacker can intercept legitimate requests (e.g. during job creation or execution) using a proxy and modify parameters to include shell metacharacters, achieving remote code execution on the appliance. This completely bypasses the intended CLISH restricted shell confinement and results in full system compromise. The vulnerabilities persist in Release 4.0 Build 14614 including the latest patch (as of the time of testing) TZM_1757588060_SEP2025_FULL.depot.
CVE-2025-67840
“—” beside the score: it is equal to the CVSS score beside it.
Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2026-03-03. A secondary CVSS source baseline 7.2; sources differ by 0.0.
Also known asEUVD-2025-208246 (ENISA EUVD) · GHSA-j46m-h6wf-3gc4 (GitHub Security Advisories)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
- CVSS v3
- 7.2
- EG Score
- 7.2HIGHmedium confidence
- EG Risk
- 34EG Risk 34/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)Severity72% × 45%Impact severity (EG Severity): CVSS 7.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation4.1% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable no (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: No fix is confirmed yet. Check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule. - EPSS PROB
- 4.1%
- EPSS %ILE
- 90th
- 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 (7.2): severity, escalated by confirmed exploitation. This CVE's 7.2 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 4.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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 or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.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 or medium mission impact; Track* at high (mission-essential systems).
No fix is confirmed yet. Check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule.
Exploitation none (CISA Vulnrichment) · Automatable no (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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
March 3, 2026
Last Modified
June 17, 2026
Advisory Details (3)
Auto-updated Aug 4, 2026GitHub - GregDurys/security-advisories · GitHub
https://github.com/GregDurys/Cohesity-TranZman-CVEsCVE-2025-67840 - Cohesity TranZman Web API Command Injection · GitHub
https://gist.github.com/GregDurys/ef7fc6a36646df927374bba8e7279270Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 40× 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 it from the CNA feed. 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). Most recent first.
Showing the most recent 99 of 120 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 21 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-01 04:38 UTCEG score recompute
- 2026-11-01 04:38 UTCGHSA enrichmentGHSA-j46m-h6wf-3gc4 · GitHub severity HIGH · GitHub CVSS 7.2
- 2026-10-31 16:31 UTCEPSS rescoreEPSS 4.1% · 90th percentile
- 2026-10-30 16:33 UTCEPSS rescoreEPSS 4.1% · 90th percentile
- 2026-10-29 16:32 UTCEPSS rescoreEPSS 4.1% · 90th percentile
- 2026-10-28 16:30 UTCEPSS rescoreEPSS 3.8% · 90th percentile
- 2026-10-27 16:30 UTCEPSS rescoreEPSS 3.8% · 90th percentile
- 2026-10-26 16:30 UTCEPSS rescoreEPSS 3.8% · 90th percentile
- 2026-10-25 16:31 UTCEPSS rescoreEPSS 3.8% · 90th percentile
- 2026-10-25 16:06 UTCEG score recompute
- 2026-10-25 01:46 UTCEG score recompute
- 2026-10-25 01:46 UTCGHSA enrichmentGHSA-j46m-h6wf-3gc4 · GitHub severity HIGH · GitHub CVSS 7.2
- 2026-10-24 16:31 UTCEPSS rescoreEPSS 3.8% · 90th percentile
- 2026-10-23 16:31 UTCEPSS rescoreEPSS 3.8% · 90th percentile
- 2026-10-22 16:33 UTCEPSS rescoreEPSS 3.8% · 90th percentile
- 2026-10-21 16:31 UTCEPSS rescoreEPSS 3.8% · 90th percentile
- 2026-10-20 16:31 UTCEPSS rescoreEPSS 3.8% · 89th percentile
- 2026-10-19 16:31 UTCEPSS rescoreEPSS 3.8% · 89th percentile
- 2026-10-18 16:31 UTCEPSS rescoreEPSS 3.8% · 89th percentile
- 2026-10-18 05:18 UTCEG score recompute
- 2026-10-17 22:55 UTCEG score recompute
- 2026-10-17 22:55 UTCGHSA enrichmentGHSA-j46m-h6wf-3gc4 · GitHub severity HIGH · GitHub CVSS 7.2
- 2026-10-17 16:33 UTCEPSS rescoreEPSS 3.8% · 89th percentile
- 2026-10-16 16:39 UTCEPSS rescoreEPSS 3.8% · 89th percentile
- 2026-10-15 16:31 UTCEPSS rescoreEPSS 3.8% · 89th percentile
Show 74 moreShow fewer
- 2026-10-14 16:31 UTCEPSS rescoreEPSS 3.8% · 89th percentile
- 2026-10-13 16:33 UTCEPSS rescoreEPSS 3.8% · 89th percentile
- 2026-10-12 16:47 UTCEG score recompute
- 2026-10-12 16:33 UTCEPSS rescoreEPSS 3.8% · 89th percentile
- 2026-10-11 20:22 UTCEG score recompute
- 2026-10-11 18:34 UTCEG score recompute
- 2026-10-11 15:09 UTCEG score recompute
- 2026-10-11 13:47 UTCEPSS rescoreEPSS 3.8% · 89th percentile
- 2026-10-10 19:59 UTCEPSS rescoreEPSS 3.8% · 89th percentile
- 2026-10-09 20:06 UTCEPSS rescoreEPSS 3.8% · 89th percentile
- 2026-10-08 17:11 UTCEPSS rescoreEPSS 3.8% · 89th percentile
- 2026-10-07 23:47 UTCEPSS rescoreEPSS 3.8% · 89th percentile
- 2026-10-06 15:17 UTCEPSS rescoreEPSS 3.8% · 89th percentile
- 2026-10-05 17:42 UTCEPSS rescoreEPSS 3.8% · 89th percentile
- 2026-10-04 23:21 UTCEPSS rescoreEPSS 3.8% · 89th percentile
- 2026-10-03 14:25 UTCEPSS rescoreEPSS 3.8% · 89th percentile
- 2026-10-01 19:49 UTCEPSS rescoreEPSS 3.8% · 89th percentile
- 2026-09-30 15:02 UTCEPSS rescoreEPSS 3.8% · 89th percentile
- 2026-09-29 15:20 UTCEPSS rescoreEPSS 3.7% · 89th percentile
- 2026-09-28 13:50 UTCEPSS rescoreEPSS 3.7% · 89th percentile
- 2026-09-26 15:58 UTCEPSS rescoreEPSS 3.7% · 89th percentile
- 2026-09-24 14:02 UTCEPSS rescoreEPSS 3.7% · 89th percentile
- 2026-09-23 13:47 UTCEPSS rescoreEPSS 3.7% · 89th percentile
- 2026-09-20 20:15 UTCEPSS rescoreEPSS 3.7% · 89th percentile
- 2026-09-18 19:27 UTCEPSS rescoreEPSS 3.7% · 89th percentile
- 2026-09-17 19:30 UTCEPSS rescoreEPSS 3.7% · 89th percentile
- 2026-09-16 14:07 UTCEPSS rescoreEPSS 3.7% · 89th percentile
- 2026-09-16 05:14 UTCEPSS rescoreEPSS 3.7% · 89th percentile
- 2026-09-15 03:10 UTCEPSS rescoreEPSS 3.7% · 89th percentile
- 2026-09-12 15:00 UTCEPSS rescoreEPSS 3.7% · 89th percentile
- 2026-09-11 14:52 UTCEPSS rescoreEPSS 3.7% · 89th percentile
- 2026-09-11 09:36 UTCEPSS rescoreEPSS 3.7% · 89th percentile
- 2026-09-10 09:34 UTCEPSS rescoreEPSS 3.7% · 89th percentile
- 2026-09-08 22:00 UTCEPSS rescoreEPSS 3.7% · 88th percentile
- 2026-09-07 16:00 UTCEPSS rescoreEPSS 3.7% · 88th percentile
- 2026-09-06 13:47 UTCEPSS rescoreEPSS 3.7% · 88th percentile
- 2026-09-04 05:06 UTCEPSS rescoreEPSS 3.7% · 88th percentile
- 2026-09-02 14:11 UTCEPSS rescoreEPSS 3.7% · 88th percentile
- 2026-09-01 13:53 UTCEPSS rescoreEPSS 3.7% · 88th percentile
- 2026-08-30 01:21 UTCEPSS rescoreEPSS 3.7% · 88th percentile
- 2026-08-28 21:40 UTCEPSS rescoreEPSS 3.7% · 88th percentile
- 2026-08-27 14:24 UTCEPSS rescoreEPSS 3.7% · 88th percentile
- 2026-08-26 14:45 UTCEPSS rescoreEPSS 3.7% · 88th percentile
- 2026-08-25 13:48 UTCEPSS rescoreEPSS 3.7% · 88th percentile
- 2026-08-24 14:16 UTCEPSS rescoreEPSS 3.7% · 88th percentile
- 2026-08-23 00:18 UTCEPSS rescoreEPSS 3.7% · 88th percentile
- 2026-08-21 23:48 UTCEPSS rescoreEPSS 3.7% · 88th percentile
- 2026-08-20 22:55 UTCEPSS rescoreEPSS 3.7% · 88th percentile
- 2026-08-19 17:03 UTCEPSS rescoreEPSS 3.7% · 88th percentile
- 2026-08-18 13:48 UTCEPSS rescoreEPSS 3.7% · 88th percentile
- 2026-08-17 13:46 UTCEPSS rescoreEPSS 3.7% · 88th percentile
- 2026-08-16 14:55 UTCEPSS rescoreEPSS 3.7% · 88th percentile
- 2026-08-16 02:14 UTCEPSS rescoreEPSS 3.7% · 88th percentile
- 2026-08-15 01:30 UTCEPSS rescoreEPSS 3.7% · 88th percentile
- 2026-08-14 21:08 UTCGHSA enrichmentGHSA-j46m-h6wf-3gc4 · GitHub severity HIGH · GitHub CVSS 7.2
- 2026-08-14 08:40 UTCEG score recompute
- 2026-08-14 08:40 UTCGHSA enrichmentGHSA-j46m-h6wf-3gc4 · GitHub severity HIGH · GitHub CVSS 7.2
- 2026-08-13 22:00 UTCEPSS rescoreEPSS 3.7% · 88th percentile
- 2026-08-13 00:31 UTCEG score recompute
- 2026-08-13 00:31 UTCGHSA enrichmentGHSA-j46m-h6wf-3gc4 · GitHub severity HIGH · GitHub CVSS 7.2
- 2026-08-12 13:50 UTCEPSS rescoreEPSS 3.7% · 88th percentile
- 2026-08-11 23:21 UTCEG score recompute
- 2026-08-11 23:21 UTCGHSA enrichmentGHSA-j46m-h6wf-3gc4 · GitHub severity HIGH · GitHub CVSS 7.2
- 2026-08-11 13:42 UTCEPSS rescoreEPSS 3.7% · 88th percentile
- 2026-08-11 05:54 UTCEG score recompute
- 2026-08-11 05:54 UTCGHSA enrichmentGHSA-j46m-h6wf-3gc4 · GitHub severity HIGH · GitHub CVSS 7.2
- 2026-08-10 23:59 UTCEPSS rescoreEPSS 3.7% · 88th percentile
- 2026-08-10 09:14 UTCGHSA enrichmentGHSA-j46m-h6wf-3gc4 · GitHub severity HIGH · GitHub CVSS 7.2
- 2026-08-09 20:45 UTCEG score recompute
- 2026-08-09 20:45 UTCGHSA enrichmentGHSA-j46m-h6wf-3gc4 · GitHub severity HIGH · GitHub CVSS 7.2
- 2026-08-09 13:46 UTCEPSS rescoreEPSS 3.7% · 88th percentile
- 2026-08-09 08:17 UTCEG score recompute
- 2026-08-09 08:17 UTCGHSA enrichmentGHSA-j46m-h6wf-3gc4 · GitHub severity HIGH · GitHub CVSS 7.2
- 2026-08-08 16:36 UTCEPSS rescoreEPSS 3.7% · 88th percentile
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2025-67840?
When was the CVE record for CVE-2025-67840 published?
Is CVE-2025-67840 actively exploited?
What is the CVSS score of CVE-2025-67840?
How do I remediate CVE-2025-67840?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2025-67840
Is Your Infrastructure Affected by CVE-2025-67840?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.