Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-26189Published 2026-02-19

CVE-2026-26189 — aquasecurity trivy-action

medium

As of 2026-02-19, CVE-2026-26189 is a MEDIUM-severity vulnerability in aquasecurity trivy-action, CVSS v3.1 5.9, EPSS 2.1% (81.5th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-26189, most recently “TeamPCP LiteLLM Supply Chain Attack — Trojaned PyPI Packages (v1.82.7/1.82.8) with Multi-Stage C2 Payload”.

CVSS v3.1
5.9/10Medium
EPSS
2.1%Higher than 81.5% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
1Campaigns referencing it
Priority
6.2/10Threadlinqs triage score
Published
CVSS v3.1 5.9 (MEDIUM) · EPSS 2.1% (higher than 81.5% of all scored CVEs) · Priority 6.2/10 · Published 2026-02-19

Last updated:

What is CVE-2026-26189?

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.

The record classifies CVE-2026-26189 under weakness class CWE-78. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs high-privilege credentials, needs no user interaction, and has high impact on confidentiality, integrity. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 233 days ago.

Severity and exploitation probability

CVSS v3.1 base score
5.9 — MEDIUM
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N
EPSS (FIRST)
2.1% probability of exploitation in the next 30 days, higher than 81.5% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
6.2/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-02-19

Is CVE-2026-26189 being exploited?

It currently carries a trending score of 25 in the Threadlinqs vulnerability feed.

Affected products and versions

  • aquasecurity: trivy-action

Affected software packages:

  • actions:aquasecurity/trivy-action — patched in 0.34.0

How to fix CVE-2026-26189

Fixed versions are recorded for 1 package: actions:aquasecurity/trivy-action 0.34.0. No vendor patch reference has been recorded for CVE-2026-26189 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-26189

1 tracked threat in the Threadlinqs corpus references CVE-2026-26189, either in the campaign’s CVE list or as an indicator on the campaign record.

Sources

Enriched from CVE.org, FIRST EPSS, GitHub Security Advisories. Last verified by Threadlinqs on .

Vendor advisory and patch

Other references