This critical vulnerability involves an active supply chain attack where malicious actors injected credential-stealing code into official software releases and GitHub Actions, impacting multiple vendors.

The flaw is categorized as CWE-506, Embedded Malicious Code, resulting from a supply chain compromise where threat actors used stolen credentials to force-push malicious commits and releases. The compromise affects the build and distribution pipeline, allowing the execution of arbitrary code with the privileges of the CI/CD environment or the end-user.

The exploitation of this vulnerability poses a severe risk to organizational security, as the injected code is designed to exfiltrate secrets and credentials. Given the CVSS score of 9.5, this incident carries a critical impact, potentially leading to unauthorized access to cloud infrastructure, source code repositories, and production environments. The inclusion in the CISA Known Exploited Vulnerabilities (KEV) catalog underscores the immediate and widespread threat this poses to enterprise supply chains.

Immediate Action: Organizations must immediately audit their environments for the affected versions and update to the safe releases: aquasecurity/trivy-action to 0.35.0, aquasecurity/setup-trivy to 0.2.6, and revert the trivy binary to 0.69.2 or 0.69.3. Furthermore, rotate all credentials, API keys, and service tokens that were present in environments where the compromised versions were utilized.

Proactive Monitoring: Review CI/CD logs for unauthorized pipeline modifications and inspect outbound network traffic from build servers for connections to suspicious external domains associated with credential exfiltration.

Compensating Controls: Implement strict version pinning in GitHub Actions and container orchestrations to prevent the automatic pulling of compromised tags or images, and utilize software composition analysis (SCA) tools to verify the integrity of third-party dependencies.

Public Exploit Available: Yes, multiple public Proof-of-Concept repositories exist on GitHub, including tools for scanning and analyzing the supply chain compromise.

The severity of this supply chain attack cannot be overstated. Because the threat actor gained the ability to exfiltrate secrets via official release channels, simply patching the software is insufficient. Security teams must treat all secrets, tokens, and credentials that were potentially exposed during the period the malicious versions were active as compromised and perform a full rotation immediately. Prioritize the transition to the specified safe versions to prevent further unauthorized access.