BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-33634High confidence

Aquasecurity Trivy Embedded Malicious Code Vulnerability

Aquasecurity · Trivy

Official source article: GitHub GHSA-69FQ-XP46-6X23 ↗. Check the applicable product and release in the original source.

9.4CriticalCVSS 4.0
Recommended action
Mitigate now

CISA confirms exploitation in the wild and lists 2026-04-09 as the remediation due date.

Mitigation available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • CISA confirms exploitation in the wild.
  • A structured source references public exploit or proof-of-concept material.
  • EPSS is 1.68% for the current model date.

Compensating controls

  • Apply the linked authoritative mitigation while planning the permanent fix.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs Aquasecurity Trivy and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Open-source package ranges5 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
GitHub Actionsaquasecurity/setup-trivyECOSYSTEM: introduced 0; fixed 0.2.60.2.6OSV record ↗aggregator derived · 10 Sep 2026
GitHub Actionsaquasecurity/trivy-actionECOSYSTEM: introduced 0; fixed 0.35.00.35.0OSV record ↗aggregator derived · 10 Sep 2026
actionsaquasecurity/setup-trivy< 0.2.60.2.6GitHub advisory ↗upstream repository advisory · 30 Mar 2026
actionsaquasecurity/trivy-action< 0.35.00.35.0GitHub advisory ↗upstream repository advisory · 30 Mar 2026
gogithub.com/aquasecurity/trivy= 0.69.4Not statedGitHub advisory ↗upstream repository advisory · 30 Mar 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-14601

CISA KEV mirrored by ENISA

Trivy is a security scanner. On March 19, 2026, a threat actor used compromised credentials to publish a malicious Trivy v0.69.4 release, force-push 76 of 77 version tags in `aquasecurity/trivy-action` to credential-stealing malware, and replace all 7 tags in `aquasecurity/setup-trivy` with malicious commits. This incident is a continuation of the supply chain attack that began in late February 2026. Following the initial disclosure on March 1, credential rotation was performed but was not atomic (not all credentials were revoked simultaneously). The attacker could have use a valid token to exfiltrate newly rotated secrets during the rotation window (which lasted a few days). This could have allowed the attacker to retain access and execute the March 19 attack. Affected components include the `aquasecurity/trivy` Go / Container image version 0.69.4, the `aquasecurity/trivy-action` GitHub Action versions 0.0.1 – 0.34.2 (76/77), and the`aquasecurity/setup-trivy` GitHub Action versions 0.2.0 – 0.2.6, prior to the recreation of 0.2.6 with a safe commit. Known safe versions include versions 0.69.2 and 0.69.3 of the Trivy binary, version 0.35.0 of trivy-action, and version 0.2.6 of setup-trivy. Additionally, take other mitigations to ensure the safety of secrets. If there is any possibility that a compromised version ran in one's environment, all secrets accessible to affected pipelines must be treated as exposed and rotated immediately. Check whether one's organization pulled or executed Trivy v0.69.4 from any source. Remove any affected artifacts immediately. Review all workflows using `aquasecurity/trivy-action` or `aquasecurity/setup-trivy`. Those who referenced a version tag rather than a full commit SHA should check workflow run logs from March 19–20, 2026 for signs of compromise. Look for repositories named `tpcp-docs` in one's GitHub organization. The presence of such a repository may indicate that the fallback exfiltration mechanism was triggered and secrets were successfully stolen. Pin GitHub Actions to full, immutable commit SHA hashes, don't use mutable version tags.

EUVD state
Present in the current official mapping
Known exploitation
Recorded by ENISA since 26 Mar 2026. Evidence sources: cisa_kev.
ENISA score
9.4 · CVSS 4.0
Advisory evidence
No linked advisory details stored yet
Recommended actionMitigate now

CISA confirms exploitation in the wild and lists 2026-04-09 as the remediation due date.

Mitigation available
01

What, why and how

Aquasecurity Trivy contains an embedded malicious code vulnerability that could allow an attacker to gain access to everything in the CI/CD environment, including all tokens, SSH keys, cloud credentials, database passwords, and any sensitive configuration in memory.

What

Aquasecurity Trivy contains an embedded malicious code vulnerability that could allow an attacker to gain access to everything in the CI/CD environment, including all tokens, SSH keys, cloud credentials, database passwords, and any sensitive configuration in memory.

Why

The product contains code that appears to be malicious in nature.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Aquasecurity Trivy contains an embedded malicious code vulnerability that could allow an attacker to gain access to everything in the CI/CD environment, including all tokens, SSH keys, cloud credentials, database passwords, and any sensitive configuration in memory.

Why

The product contains code that appears to be malicious in nature.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Confirmed in the wild

CISA added this CVE to its Known Exploited Vulnerabilities catalogue on 2026-03-26.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Embedded Malicious Code → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-506 ↗

CWE-506: Embedded Malicious Code. The product contains code that appears to be malicious in nature.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATNoneAttack requirements: No additional deployment or execution condition is required.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.VCHighVulnerable-system confidentiality: A successful attack can cause a major loss.VIHighVulnerable-system integrity: A successful attack can cause a major loss.VAHighVulnerable-system availability: A successful attack can cause a major loss.SCHighSubsequent-system confidentiality: A successful attack can cause a major loss.SIHighSubsequent-system integrity: A successful attack can cause a major loss.SAHighSubsequent-system availability: A successful attack can cause a major loss.
Post-exploitation / living off the land
Stolen credentials, tokens and legitimate administration functions may provide continued access without deploying a large custom toolset.
NetworkCWE-506CISA KEVPublic exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-14601Known-exploited evidence recorded

Trivy is a security scanner. On March 19, 2026, a threat actor used compromised credentials to publish a malicious Trivy v0.69.4 release, force-push 76 of 77 version tags in `aquasecurity/trivy-action` to credential-stealing malware, and replace all 7 tags in `aquasecurity/setup-trivy` with malicious commits. This incident is a continuation of the supply chain attack that began in late February 2026. Following the initial disclosure on March 1, credential rotation was performed but was not atomic (not all credentials were revoked simultaneously). The attacker could have use a valid token to exfiltrate newly rotated secrets during the rotation window (which lasted a few days). This could have allowed the attacker to retain access and execute the March 19 attack. Affected components include the `aquasecurity/trivy` Go / Container image version 0.69.4, the `aquasecurity/trivy-action` GitHub Action versions 0.0.1 – 0.34.2 (76/77), and the`aquasecurity/setup-trivy` GitHub Action versions 0.2.0 – 0.2.6, prior to the recreation of 0.2.6 with a safe commit. Known safe versions include versions 0.69.2 and 0.69.3 of the Trivy binary, version 0.35.0 of trivy-action, and version 0.2.6 of setup-trivy. Additionally, take other mitigations to ensure the safety of secrets. If there is any possibility that a compromised version ran in one's environment, all secrets accessible to affected pipelines must be treated as exposed and rotated immediately. Check whether one's organization pulled or executed Trivy v0.69.4 from any source. Remove any affected artifacts immediately. Review all workflows using `aquasecurity/trivy-action` or `aquasecurity/setup-trivy`. Those who referenced a version tag rather than a full commit SHA should check workflow run logs from March 19–20, 2026 for signs of compromise. Look for repositories named `tpcp-docs` in one's GitHub organization. The presence of such a repository may indicate that the fallback exfiltration mechanism was triggered and secrets were successfully stolen. Pin GitHub Actions to full, immutable commit SHA hashes, don't use mutable version tags.

Official EUVD record ↗
BSI · German · WID-SEC-2026-0898Aqua Security Trivy: Schwachstelle ermöglicht vollständige Kompromittierung des Systems

Ein Angreifer kann eine Schwachstelle in Aqua Security Trivy ausnutzen, um das vollständige System zu kompromittieren.

Official advisory ↗
Canadian Centre for Cyber Security · English · AV26-283Aqua Security security advisory (AV26-283) – Update 1

On March 22, 2026, Aqua Security published a security advisory to address a critical vulnerability in the following products: Open-source reporting indicates that CVE-2026-33634 has been exploited.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260325Security Bulletin 25 Mar 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 25 Mar 2026, published on 25 March 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-009188Aqua Security等の複数ベンダの製品における埋め込まれた悪意のあるコードに関する脆弱性

Trivyはセキュリティスキャナーです。2026年3月19日に、攻撃者は侵害された認証情報を使用して悪意のあるTrivy v0.69.4リリースを公開しました。`aquasecurity/trivy-action`の77のバージョンタグのうち76を認証情報窃取マルウェアに強制プッシュし、`aquasecurity/setup-trivy`の全7タグを悪意のあるコミットに置き換えました。この事件は2026年2月下旬に始まったサプライチェーン攻撃の続きです。3月1日の初期公開後に認証情報のローテーションが行われましたが、それは原子操作ではなく（一度にすべての認証情報が無効化されたわけではありません）、攻撃者は有効なトークンを使用してローテーション中に新たにローテーションされた秘密情報を数日間にわたり持ち出せた可能性があります。これにより攻撃者はアクセスを維持し、3月19日の攻撃を実行できた可能性があります。影響を受けるコンポーネントは、`aquasecurity/trivy`のGo / コンテナイメージバージョン0.69.4、`aquasecurity/trivy-action`のGitHub Actionバージョン0.0.1から0.34.2まで（76/77）、および`aquasecurity/setup-trivy`のGitHub Actionバージョン0.2.0から0.2.6までで、0.2.6は安全なコミットによる再作成前のものです。既知の安全なバージョンには、Trivyバイナリの0.69.2および0.69.3、trivy-actionの0.35.0、setup-trivyの0.2.6があります。さらに秘密情報の安全を確保するために追加の緩和策を取ってください。侵害されたバージョンが環境で実行された可能性がある場合は、影響を受けるパイプラインでアクセス可能なすべての秘密情報を露出したものとして扱い、直ちにローテーションしてください。組織は任意のソースからTrivy v0.69.4をプルまたは実行したかを確認し、影響を受けたアーティファクトを直ちに削除してください。`aquasecurity/trivy-action`や`aquasecurity/setup-trivy`を使用している全てのワークフローをレビューし、完全なコミットSHAではなくバージョンタグを参照している場合は、2026年3月19日から20日のワークフローログを調査して侵害の兆候を確認してください。GitHub組織内に`tpcp-docs`という名前のリポジトリが存在する場合、それはフォールバックの情報持ち出しメカニズムが起動して秘密情報の窃取が成功した可能性を示しています。GitHub Actionsは完全かつ不変のコミットSHAハッシュに固定し、可変のバージョンタグを使用しないでください。

Official advisory ↗
KISA KrCERT/CC · Korean · KNVD-6743AquaSecurity 제품 보안 업데이트 권고

AquaSecurity trivy에서 발생하는 Embedded Malicious Code 취약점(CVE-2026-33634) [1][2]

Official advisory ↗
KISA KrCERT/CC · Korean · KNVD-6740美 CISA 발표 주요 Exploit 정보공유(Update. 2026-03-26)

Aquasecurity Trivy Embedded Malicious Code Vulnerability

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Mitigation available
Affected
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
Apply the mitigation in the linked authoritative guidance while planning the vendor's permanent fix.
Workaround
A mitigation or workaround reference is available from the source linked below; validate it against the affected product and version.
04

Evidence and provenance

Published 23 Mar 2026 · Last source change 30 Mar 2026, 14:40 UTC · CWE-506 · Embedded Malicious Code

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-14601
Product sourceCISA KEV
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. BlackTree coverageBlackTree article coverage changed from no BlackTree article to 1 BlackTree article.
    Before
    no BlackTree article
    After
    1 BlackTree article
    BlackTree editorial ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 0.2.6; < 0.35.0; = 0.69.4; >= 1.82.7, <= 1.82.8; >= 4.87.1, <= 4.87.2 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    setup-trivy: < 0.2.6; trivy-action: < 0.35.0; trivy: = 0.69.4; LiteLLM: >= 1.82.7, <= 1.82.8; telnyx: >= 4.87.1, <= 4.87.2 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Added to CISA KEV
Mitigation reference recorded
ENISA EUVD · EUVD-2026-14601↗CISA KEV record↗Public exploit reference · GitHub GHSA-69FQ-XP46-6X23↗Mitigation reference↗Vendor advisory↗Mitigation reference↗Public exploit reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-33634 · cve.blacktree.nl