CVE-2026-67180

HIGHPre-NVD 8.48.4
EchelonGraph scoreHIGH confidence

Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2026-08-11. a secondary CVSS source baseline 8.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.4Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Google Turbinia allows arbitrary command execution via worker tasks. An attacker with privileges to submit a processing request or influence an evidence path/name obtains code execution on the worker fleet. Fixed on 2026-07-10.

CVSS v3
8.4
EG Score
8.4(high)
EG Risk
54(Track*)
EG Risk 54/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity84% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

August 11, 2026

Last Modified

August 17, 2026

Advisory Details (3)

Auto-updated Aug 11, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
github_pr

Avoid shell execution in forensic workers

Fix merged in google/turbinia PR #1631 on 2026-07-10 — awaiting tagged release

https://github.com/google/turbinia/pull/1631
generic

Command injection (RCE) in worker tasks via evidence path interpolated into a shell=True command · Issue #1629 · google/turbinia · GitHub

https://github.com/google/turbinia/issues/1629

Vendor Advisories for CVE-2026-67180(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 27× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 21:13 UTCGHSA enrichment
  3. 2026-08-20 08:56 UTCGHSA enrichment
  4. 2026-08-19 20:38 UTCEG score recompute
  5. 2026-08-19 20:38 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 08:20 UTCGHSA enrichment
  8. 2026-08-18 20:02 UTCEG score recompute
  9. 2026-08-18 20:02 UTCGHSA enrichment
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-18 07:45 UTCGHSA enrichment
  12. 2026-08-17 19:28 UTCEG score recompute
  13. 2026-08-17 19:28 UTCGHSA enrichment
  14. 2026-08-17 18:36 UTCEG score recompute
  15. 2026-08-17 18:35 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 08:00 UTCGHSA enrichment
  18. 2026-08-16 19:43 UTCEG score recompute
  19. 2026-08-16 19:43 UTCGHSA enrichment
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 07:26 UTCEG score recompute
  22. 2026-08-16 07:26 UTCGHSA enrichment
  23. 2026-08-15 19:08 UTCGHSA enrichment
  24. 2026-08-15 06:50 UTCEG score recompute
  25. 2026-08-15 06:50 UTCGHSA enrichment
Show 15 more
  1. 2026-08-15 01:30 UTCEPSS rescore
  2. 2026-08-14 18:20 UTCGHSA enrichment
  3. 2026-08-14 06:03 UTCEG score recompute
  4. 2026-08-14 06:03 UTCGHSA enrichment
  5. 2026-08-13 22:00 UTCEPSS rescore
  6. 2026-08-13 17:45 UTCGHSA enrichment
  7. 2026-08-13 05:27 UTCGHSA enrichment
  8. 2026-08-12 17:10 UTCEG score recompute
  9. 2026-08-12 17:10 UTCGHSA enrichment
  10. 2026-08-12 13:51 UTCEPSS rescore
  11. 2026-08-12 04:53 UTCEG score recompute
  12. 2026-08-12 04:53 UTCGHSA enrichment
  13. 2026-08-11 16:35 UTCEG score recompute
  14. 2026-08-11 16:06 UTCEG score recompute
  15. 2026-08-11 16:06 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-67180?
CVE-2026-67180 is a high vulnerability published on August 11, 2026. Google Turbinia allows arbitrary command execution via worker tasks. An attacker with privileges to submit a processing request or influence an evidence path/name obtains code execution on the worker fleet. Fixed on 2026-07-10.
When was CVE-2026-67180 disclosed?
CVE-2026-67180 was first published in the National Vulnerability Database on August 11, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-67180 actively exploited?
CVE-2026-67180 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.8% of all scored CVEs.
What is the CVSS score of CVE-2026-67180?
CVE-2026-67180 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-67180?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-67180, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-67180

Explore →

Is Your Infrastructure Affected by CVE-2026-67180?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.