CVE-2026-33634: Aquasecurity Trivy Embedded Malicious Code Vulnerability

Trivy is a tool used in continuous integration and continuous delivery pipelines to scan container images and other artifacts for security issues. CVE-2026-33634 is an embedded malicious code vulnerability in Aquasecurity Trivy that could let an attacker obtain every credential and secret present in the CI/CD environment, including tokens, SSH keys, cloud credentials, database passwords, and configuration data held in memory.

How it works

The weakness is categorized as CWE-506, embedded malicious code. In this class of flaw, unauthorized code is present inside the shipped product and can execute within the runtime environment. An attacker who can reach the affected Trivy process gains the ability to read all material in the process address space and any accessible environment variables or mounted secrets typical of CI/CD workloads.

Am I affected? How to find it in your systems

Trivy commonly runs as a command-line binary or container inside build agents, pipeline runners, and developer workstations. Inventory every location where the Trivy binary or container image is executed, including source repositories, CI configuration files, and container registries. Check the exact version and configuration of each instance against the vendor advisory, because only the advisory lists the precise releases and build artifacts that contain the embedded code. Review process execution logs and pipeline telemetry for unexpected outbound connections or access to secret stores that coincide with Trivy runs.

How to remediate

Apply the vendor-supplied update referenced in the official advisory as the primary remediation. After patching, rebuild all pipeline images and agents that embed Trivy so that the updated binary replaces any prior instances. Review CI/CD configurations to ensure Trivy runs with the minimum required permissions and that secrets are not unnecessarily exposed to the scanning process.

If you can't patch immediately

• Isolate the build agents and pipeline runners that execute Trivy on a dedicated network segment with strict egress controls.
• Follow applicable CISA BOD 22-01 guidance for any cloud-hosted CI/CD services that invoke the affected Trivy version.
• Disable or replace Trivy with an alternative scanner until the vendor update can be deployed.
• Increase monitoring of secret-access APIs and outbound network traffic from build nodes for anomalous patterns.

If your data may have been exposed

Compromise of CI/CD tooling frequently results in credential theft that leads to further breaches. Organizations can run a free exposure scan of their domains and email addresses against known breach data to determine whether any credentials have already appeared in public repositories or data dumps.