Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-9p44-j4g5-cfx5 | Trivy Action has a script injection via sourced env file in composite action |
Thu, 26 Feb 2026 03:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Aquasec
Aquasec trivy Action |
|
| CPEs | cpe:2.3:a:aquasec:trivy_action:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Aquasec
Aquasec trivy Action |
Fri, 20 Feb 2026 10:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Aquasecurity
Aquasecurity trivy-action |
|
| Vendors & Products |
Aquasecurity
Aquasecurity trivy-action |
Fri, 20 Feb 2026 01:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 19 Feb 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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=<input>` 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. | |
| Title | Trivy Action has a script injection via sourced env file in composite action | |
| Weaknesses | CWE-78 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-02-19T21:23:33.970Z
Reserved: 2026-02-11T19:56:24.812Z
Link: CVE-2026-26189
Updated: 2026-02-19T20:57:41.132Z
Status : Analyzed
Published: 2026-02-19T20:25:42.120
Modified: 2026-02-26T02:55:00.643
Link: CVE-2026-26189
No data.
OpenCVE Enrichment
Updated: 2026-04-18T11:45:44Z
Github GHSA