llamaCVEVulnerability Intelligence
/
setup-trivy

CVE-2026-33634

Secret theft in compromised GitHub Actions supply chain

An attacker could steal credentials and other secrets from pipelines that pulled or ran the compromised releases.

CISA KEV · explotación activaCrítica · en CISA KEV, EPSS ≥ 10 %Explotación activaSin parche publicado
Descargar PNG JSON
CVSS 4.0
9.4
Crítica
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 Fuente: CNA
8.8NVD · CVSS 3.1CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
ExplotaciónActivaEn CISA KEV desde 26 mar 2026
Exploits públicos0Ninguno conocido
ParcheSin parcheEl fabricante no ha publicado corrección
Exposición240 dDesde la divulgación, 23 mar 2026, 4:47 p. m.
EPSS ≥ 10 %27 oct 2026Fecha en que la probabilidad de explotación superó el umbral
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Modificada
Explotación
CISA KEV
Umbral EPSS
Remediación
Plazo KEV
Monitoreo
Detectada
Verificada
23 mar 26
26 mar 26
30 mar 26
9 abr 26
22 oct 26
27 oct 26
14 nov 26
19 nov 26
23 mar 26
23 may 26
22 jul 26
20 sept 26
19 nov 26
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-33634 divulgada · CVSS 9.4 (CNA)
Explotación CISA KEV Agregada al catálogo de vulnerabilidades explotadas
Divulgación Modificada Última actualización del registro
Remediación Plazo KEV Fecha límite de remediación para agencias federales (EE. UU.)
Monitoreo Detectada Ingresó al índice
Explotación Umbral EPSS La probabilidad de explotación supera el 10 %
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Resumen generado por IA · CC-BY 4.0 · 13 nov 2026

Trivy, a security scanner from aquasecurity, and its GitHub Actions trivy-action and setup-trivy were tampered with in a supply chain attack, as were the downstream LiteLLM and telnyx packages. The malicious releases ran credential-stealing malware that harvested secrets such as SSH keys, cloud and Kubernetes credentials, tokens, and .env files from CI runners and sent them to attacker infrastructure. The flaw is reachable remotely over the network with only low-level access needed and no user interaction, and it is listed as exploited in attacks by CISA.

Affects Trivy v0.69.4, trivy-action tags 0.0.1–0.34.2, unpinned setup-trivy, and some Docker Hub images, plus LiteLLM 1.82.7–1.82.8 and telnyx 4.87.1–4.87.2. Fixed in trivy-action 0.35.0 and setup-trivy 0.2.6.

¿Qué significa?Attackers briefly compromised the Trivy ecosystem and published malicious Trivy releases and GitHub Actions tags. These ran a credential-stealing infostealer that harvested secrets such as SSH keys, cloud and Kubernetes credentials, tokens and .env files from CI runners and sent them to attacker infrastructure.
¿Quién está afectado?Affected are the Trivy binary or container image v0.69.4 (or latest during the exposure window), Docker Hub images v0.69.5 and v0.69.6, trivy-action tags 0.0.1–0.34.2 (all except 0.35.0), and setup-trivy used without pinning to a safe commit. Downstream, LiteLLM 1.82.7 or 1.82.8 installed from PyPI on March 24, 2026 between 10:39 and 16:00 UTC is also listed, as are telnyx 4.87.1–4.87.2. Readers can check the Trivy version in use, the tag referenced in their workflow files, and their pip install history for LiteLLM.
¿Qué hacer?Use trivy-action 0.35.0 and setup-trivy 0.2.6. The advisory also lists Trivy binary v0.69.2 and v0.69.3 as safe versions. Pin GitHub Actions to full, immutable commit SHA hashes instead of version tags, and rotate all secrets that may have been exposed.
Descripción original del registro

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.

Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
Used Trivy binary or container image v0.69.4 (or latest during the exposure window) from GitHub, Deb, RPM, GHCR, ECR Public or Docker Hub“trivy binaries version v0.69.4 (or latest during the exposure window) distributed via GitHub, Deb, RPM.”
02
Used trivy-action by a tag other than 0.35.0 (0.0.1 – 0.34.2)“Any tags prior except 0.35.0 (0.0.1 – 0.34.2) to reference the action.”
03
Used setup-trivy without pinning to a safe commit“Any version without pinning.”
04
Used Docker Hub trivy images v0.69.5 or v0.69.6 (or latest during the exposure window)“trivy container images v0.69.5 and v0.69.6 (or latest during the exposure window) distributed via Docker Hub.”
05
Downstream: installed LiteLLM 1.82.7 or 1.82.8 from PyPI on March 24, 2026 (10:39–16:00 UTC)“You installed or upgraded LiteLLM via pip on March 24, 2026 , between 10:39 UTC and 16:00 UTC”
¿Quién debe revisar?Teams that ran Trivy v0.69.4 or the 0.69.5/0.69.6 Docker images, or trivy-action/setup-trivy tags in GitHub Actions on March 19–22, 2026, or installed LiteLLM 1.82.7/1.82.8.
No protegeRotating tags is not enough: any secrets reachable by affected pipelines must be rotated.
MitigaciónPin GitHub Actions to full, immutable commit SHA hashes instead of version tags, and rotate all secrets that may have been exposed.
Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · NVD
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:L
BajaAlta
PrivilegiosPR:L
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:H
AltoBajoNinguno
IntegridadI:H
AltoBajoNinguno
DisponibilidadA:H
AltoBajoNinguno
Versiones

Rangos afectados

Afectada Corregida Última
setup-trivy · aquasecurity/setup-trivy< 0.2.6
trivy-action · aquasecurity/trivy-action< 0.35.0
github.com/aquasecurity/trivy≥ 0.69.4
LiteLLM≥ 1.82.7 ≤ 1.82.8
telnyx≥ 4.87.1 ≤ 4.87.2
0.2.6
0.35.0
0.69.4
v0.76.2
1.82.7
1.82.8
4.87.1
4.87.2
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
gogithub.com/aquasecurity/trivy
Sin parche — — v0.76.2 afectada
Versiones corregidas0.2.60.35.0
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Fabricantehttps://github.com/aquasecurity/trivy/security/advisories/GHSA-69fq-xp46-6x23
Fabricantehttps://github.com/team-telnyx/telnyx-python/security/advisories/GHSA-955r-262c-33jc
Fabricantehttps://docs.litellm.ai/blog/security-update-march-2026
Otrahttps://github.com/BerriAI/litellm/issues/24518
Otrahttps://futuresearch.ai/blog/litellm-pypi-supply-chain-attack
Otrahttps://github.com/aquasecurity/trivy/discussions/10425
Otrahttps://github.com/pypa/advisory-database/tree/main/vulns/litellm/PYSEC-2026-2.yaml
Otrahttps://inspector.pypi.io/project/litellm/1.82.7/packages/79/5f/b6998d42c6ccd32d36e12661f2734602e72a576d52a51f4245aef0b20b4d/litellm-1.82.7-py3-none-any.whl/litellm/proxy/proxy_server.py#line.130
Otrahttps://inspector.pypi.io/project/litellm/1.82.8/packages/f6/2c/731b614e6cee0bca1e010a36fd381fba69ee836fe3cb6753ba23ef2b9601/litellm-1.82.8.tar.gz/litellm-1.82.8/litellm_init.pth#line.1
Otrahttps://www.wiz.io/blog/teampcp-attack-kics-github-action

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.