Sign in Sign up
JA · EN · FR
SecPulse
DevOps / CI-CD
CVE-2026-33634 CISA KEV high

[KEV] Vulnerability in Aquasecurity Trivy (CVE-2026-33634)

DevOps / CI-CD

Summary

Vulnerability in Aquasecurity Trivy (CVE-2026-33634). Risk of unauthorized operations or information disclosure. Listed in CISA KEV — actively exploited. Mitigation: upgrade to 0.35.0 or later.

Original description

The description as published by the source.

On March 19, 2026, a threat actor used compromised credentials to publish a malicious Trivy v0.69.4 release.

Source: CISA Known Exploited Vulnerabilities NVD GitHub Advisory CISA KEV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-33634 has been found in Aquasecurity Trivy.
Risk of unauthorized operations or information disclosure.
Note: CISA has officially confirmed this is actively exploited in the wild. Treat it with elevated urgency.
What to do: upgrade Aquasecurity Trivy to 0.35.0 or later.
If unsure, ask your IT team or search "Aquasecurity Trivy CVE-2026-33634" on the vendor's site.

CVE-2026-33634 (Aquasecurity Trivy) — CWE-506
Patched: 0.35.0 — apply immediately
Listed in CISA KEV — actively exploited, treat as top priority.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-506) exists in Aquasecurity Trivy.

📍 Affected scope

Check the vendor advisory for the affected versions of Aquasecurity Trivy.

🔥 Severity

Severity: High. Risk of unauthorized operations or information disclosure. Listed in CISA KEV — actively exploited in the wild, treat as top priority.

🔧 How to fix

Update to 0.35.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/aquasecurity/trivy' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/aquasecurity/trivy' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/aquasecurity/trivy を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Consider incident declaration escalate 
    Notify SOC / on-call

    CISA KEV登録済 = 実環境で悪用が観測されている。侵入の兆候があればインシデント対応宣言、無くてもパッチ適用までWAF強化を最優先で。

  3. 3
    Apply patch patch 
    Upgrade Aquasecurity Trivy to 0.35.0

    ステージング環境で 0.35.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Go github.com/aquasecurity/trivy
[{"type":"SEMVER","events":[{"introduced":"0.69.4"}]}]
GitHub Actions aquasecurity/trivy-action
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.35.0"}]}]
GitHub Actions aquasecurity/setup-trivy
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.2.6"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details