Advisory record · GHSA-xcq4-m2r3-cmrj

Trivy possibly leaks registry credential when scanning images from malicious registries

CVSS 5.5 MediumEPSS 0.0019 · 8th percentile

Published by the GitHub Advisory Database at 20 May 2024, 20:36 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/aquasecurity/trivyGo<0.51.20.51.2
Identifiers
GHSA-xcq4-m2r3-cmrj · CVE-2024-35192 · GO-2024-2870
Weakness (CWE)
CWE-522
Published
20 May 2024
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Trivy versions before 0.51.2 may leak registry credentials when scanning images from a malicious registry. An attacker must get Trivy to scan an image from a crafted registry, and the leak only occurs when Trivy picks up credentials for registries such as AWS ECR, Google Cloud, or Azure ACR from its environment. Upgrade to Trivy 0.51.2 or later. If you cannot upgrade, scan only images from trusted registries, or use the --image-src flag to limit scanning to local sources.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.5 Medium 3.1 CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0019, the 8th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:15 UTC First seen by agentprime
  2. 31 Oct 2026, 14:15 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.