Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2026-55092 high CVSS 7.5

Path Traversal in github.com/aquasecurity/trivy (CVE-2026-55092)

Summary

path traversal in github.com/aquasecurity/trivy (CVE-2026-55092). Data can be tampered with by attackers. Exploitable via ``org.opencontainers.image.title``. Mitigation: upgrade to `0.71.1` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-55092** has been found in github.com/aquasecurity/trivy. Attackers can target a specific entry point like ``org.opencontainers.image.title`` over the network to misuse the product. Data can be tampered with by attackers. CVSS score: 7.5/10. What to do: upgrade github.com/aquasecurity/trivy to **0.71.1** or later. If unsure, ask your IT team or search "github.com/aquasecurity/trivy CVE-2026-55092" on the vendor's site.
CVE-2026-55092 (github.com/aquasecurity/trivy) — CWE-22 / CVSS v3 7.5 Attack vector: remote (network-reachable) / unauthenticated / no user interaction Attack surface: `org.opencontainers.image.title` / `TRIVY_DB_REPOSITORY` / `db.repository` / `trivy.yaml` Patched: `0.71.1` — apply immediately Workaround: If upgrading is not immediately possible, do not download Trivy artifacts (vulnerability database, Java database, misconfiguration checks bundle, modules, etc.) from OCI repositories you do not operate or trust. 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
**Path traversal** (CWE-22) exists in github.com/aquasecurity/trivy. Attackers reach the vulnerable code path via ``org.opencontainers.image.title`` without authentication.
📍 Affected scope
github.com/aquasecurity/trivy — . Attack surface: `org.opencontainers.image.title` / `TRIVY_DB_REPOSITORY` / `db.repository` / `trivy.yaml`.
🔥 Severity
Severity: High (CVSS 7.5/10). Data can be tampered with by attackers
🔧 How to fix
Update to **0.71.1**.
🛡️ Workaround
Workaround: If upgrading is not immediately possible, do not download Trivy artifacts (vulnerability database, Java database, misconfiguration checks bundle, modules, etc.) from OCI repositories you do not operate or trust.
🔍 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 (7 steps)

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. 5
    Apply temporary workaround mitigate 
    If upgrading is not immediately possible, do not download Trivy artifacts (vulnerability database, Java database, misconfiguration checks bundle, modules, etc.) from OCI repositories you do not operate or trust.

    パッチが適用されるまでの応急処置として、If upgrading is not immediately possible, do not download Trivy artifacts (vulnerability database, Java database, misconfiguration checks bundle, modules, etc.) from OCI repositories you do not operate or trust. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 6
    Apply patch patch 
    Upgrade github.com/aquasecurity/trivy to 0.71.1

    ステージング環境で 0.71.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

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

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

Affected packages

go github.com/aquasecurity/trivy
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.71.1"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →