Trivy Action runs Trivy as GitHub action to scan a Docker container image for vulnerabilities. A command injection vulnerability exists in aquasecurity/trivy-action versions 0.31.0 through 0.33.1 due to improper handling of action inputs when exporting environment variables. The action writes export VAR= lines to trivy_envs.txt based on user-supplied inputs and subsequently sources this file in entrypoint.sh. Because input values are written without appropriate shell escaping, attacker-controlled input containing shell metacharacters (e.g., $(...), backticks, or other command substitution syntax) may be evaluated during the sourcing process. This can result in arbitrary command execution within the GitHub Actions runner context. Version 0.34.0 contains a patch for this issue. The vulnerability is exploitable when a consuming workflow passes attacker-controlled data into any action input that is written to trivy_envs.txt. Access to user input is required by the malicious actor. Workflows that do not pass attacker-controlled data into trivy-action inputs, workflows that upgrade to a patched version that properly escapes shell values or eliminates the source ./trivy_envs.txt pattern, and workflows where user input is not accessible are not affected.
CVE-2026-26189
This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 1.3%, top 32% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EG Score
- 8.1(medium)
- EG Risk
- 41(Track)EG Risk 41/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 computedSeverity81% × 45%Exploitation1% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 70%
- KEV
- Not listed
Published
February 19, 2026
Last Modified
June 17, 2026
Advisory Details (3)
Auto-updated Jul 27, 2026script injection via sourced env file in composite action · Advisory · aquasecurity/trivy-action · GitHub
https://github.com/aquasecurity/trivy-action/security/advisories/GHSA-9p44-j4g5-cfx5commit bc61dc55704e (aquasecurity/trivy-action)
Patch available: aquasecurity/trivy-action 0.35.0 (contains commit bc61dc55704e)
https://github.com/aquasecurity/trivy-action/commit/bc61dc55704e2d5704760f3cdab0d09acf16e4cacommit 7aca5acc9500 (aquasecurity/trivy-action)
Patch available: aquasecurity/trivy-action 0.35.0 (contains commit 7aca5acc9500)
https://github.com/aquasecurity/trivy-action/commit/7aca5acc9500b463826cc47a47a65ad7d404b045Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 23× 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.
- 2026-09-19 15:03 UTCOSV refresh
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-16 14:07 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-12 15:01 UTCEPSS rescore
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-08-31 18:34 UTCOSV refresh
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
Show 33 moreShow fewer
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 09:33 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 01:44 UTCEG score recompute
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-12 02:00 UTCEG score recompute
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 07:09 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-09 21:56 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 09:09 UTCEG score recompute
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 21:24 UTCEG score recompute
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 03:25 UTCEG score recompute
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 20:06 UTCEG score recompute
- 2026-08-02 02:26 UTCEPSS rescore
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:27 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-27 14:46 UTCEG score recompute
- 2026-07-27 13:55 UTCOSV refresh
Related CVEs(same CWE)
Same CWE
10 shownCWE-78
Frequently asked(5)
What is CVE-2026-26189?
When was CVE-2026-26189 disclosed?
Is CVE-2026-26189 actively exploited?
What is the CVSS score of CVE-2026-26189?
How do I remediate CVE-2026-26189?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-26189
Is Your Infrastructure Affected by CVE-2026-26189?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.