CVE-2026-54168
MediumCVSS 6.5Exploitation Probability (EPSS)
Low risk46th percentile - higher than 46% of all known CVEs
Summary
In Pipelines-as-Code prior to 0.37.8, 0.39.6, 0.42.1, and 0.48.0, a GitHub App installation token created during webhook processing is not scoped to the repository that triggered the event when the App is installed across multiple repositories. A user with push access to one repository can submit a PipelineRun with a remote task annotation targeting a private repository in the same installation, disclosing that repository's Tekton definitions.
Risk Assessment
Tekton definitions of a private repository may be disclosed. The demonstrated impact is read-only and does not provide write access.
Recommendation
Update Pipelines-as-Code to versions 0.37.8, 0.39.6, 0.42.1, or 0.48.0, where the issue is fixed.
Other vulnerabilities in Pipelines-as-Code
Original NVD description (English source)
Pipelines-as-Code is a CI/CD system that lets users define Tekton pipelines in source code repositories. Prior to 0.37.8, 0.39.6, 0.42.1, and 0.48.0, a GitHub App installation token created during webhook processing is not scoped to the repository that triggered the event when the App is installed across multiple repositories. A user with push access to one repository can submit a PipelineRun containing a pipelinesascode.tekton.dev/task remote task annotation that targets a private repository in the same installation. When ScopeTokenToListOfRepos returns no explicit scope, the missing triggering repository ID leaves the token able to access the entire installation. Pipelines-as-Code resolves and inlines the remote private task with that token, disclosing the repository's Tekton definitions. The demonstrated impact is read-only and does not provide write access. This issue is fixed in versions 0.37.8, 0.39.6, 0.42.1, and 0.48.0.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS

