TeamPCP & Trivy Exploit: Why Open Execution Pipelines Fail

In March 2026, a significant security breach known as the TeamPCP exploit exposed vulnerabilities in CI/CD pipelines that utilize open execution models, where third-party code runs with full privileges. The attack compromised GitHub Actions, allowing the attackers to turn Trivy, a widely used vulnerability scanner, into a tool for harvesting credentials like AWS tokens and SSH keys. This incident, tracked as CVE-2026-33634, affected over 10,000 workflows and highlighted the inherent risks of mutable tags and third-party code execution in open pipelines. The breach spanned various ecosystems, leading to widespread data exposure and demonstrating the need for more secure governed execution pipelines, like those provided by Harness, which control execution through policy gates, customer-owned infrastructure, and scoped credentials. As the industry moves towards more automated and AI-driven processes, the importance of secure pipeline architectures that limit credential exposure and enforce strict execution controls becomes increasingly vital to prevent similar attacks.