de la publicación al arma
Apareció en 1 incidente(s) que verificamos
Quién la explota — 2
Grupos conocidos por explotar esta vulnerabilidad (atribución MITRE ATT&CK).
Acción exigida por CISAplazo federal: 2026-04-09
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
En resumen
La herramienta de seguridad Trivy fue comprometida el 19 de marzo de 2026, cuando atacantes usaron credenciales robadas para lanzar versiones maliciosas que roban contraseñas y secretos de usuarios que las instalaron. Esto ocurrió porque las credenciales se cambiaron lentamente tras una violación anterior, dando a los atacantes tiempo para robar las nuevas también.
Detalle técnico
CWE-506 (Código Malicioso Incrustado) - Atacante explotó rotación incompleta de credenciales (revocación no-atómica) para mantener acceso mediante tokens válidos durante la ventana de rotación (varios días), permitiendo republicación de artefactos comprometidos en múltiples repositorios Trivy y GitHub Actions con cargas de robo de credenciales. Afectados: Trivy v0.69.4, trivy-action v0.0.1–0.34.2 (76/77 tags), setup-trivy v0.2.0–0.2.6. Impacto: exposición de todos los secretos accesibles a los pipelines CI/CD afectados.
Resumen generado y traducido por IA a partir de la descripción oficial.
El análisis completo de esta CVE está disponible en portugués →
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.
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
⚠ Recursos públicos, para evaluar la exposición de sistemas que controlas o estás autorizado a probar. Prueba solo con autorización.
CVEs relacionadas — aquasecurity trivy
En el mismo producto, de las más peligrosas a las menos.