CVE-2026-26189

HIGHNVD 8.18.1
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 1.3%, top 33% 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).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.1Exploit: None knownExposed: 0

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

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.

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 computed
Severity81% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
67%
KEV
Not listed

Published

February 19, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Jul 27, 2026
Patch available. Sources: github_commit, github.
github Patch Available

script injection via sourced env file in composite action · Advisory · aquasecurity/trivy-action · GitHub

https://github.com/aquasecurity/trivy-action/security/advisories/GHSA-9p44-j4g5-cfx5
github_commit Patch Available

commit bc61dc55704e (aquasecurity/trivy-action)

Patch available: aquasecurity/trivy-action 0.35.0 (contains commit bc61dc55704e)

https://github.com/aquasecurity/trivy-action/commit/bc61dc55704e2d5704760f3cdab0d09acf16e4ca
github_commit Patch Available

commit 7aca5acc9500 (aquasecurity/trivy-action)

Patch available: aquasecurity/trivy-action 0.35.0 (contains commit 7aca5acc9500)

https://github.com/aquasecurity/trivy-action/commit/7aca5acc9500b463826cc47a47a65ad7d404b045

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 3× in last 7d / 3× 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-07-28 15:36 UTCEPSS rescore
  2. 2026-07-27 14:46 UTCEG score recompute
  3. 2026-07-27 13:55 UTCOSV refresh

Frequently asked(5)

What is CVE-2026-26189?
CVE-2026-26189 is a high vulnerability published on February 19, 2026. 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…
When was CVE-2026-26189 disclosed?
CVE-2026-26189 was first published in the National Vulnerability Database on February 19, 2026, with the most recent update on June 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-26189 actively exploited?
CVE-2026-26189 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 32.5% of all scored CVEs.
What is the CVSS score of CVE-2026-26189?
CVE-2026-26189 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-26189?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-26189, 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-26189

Explore →

Is Your Infrastructure Affected by CVE-2026-26189?

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