Pipelines-as-Code: Unscoped GitHub App installation token allows unauthorized access to private repositories via remote task resolution

Summary

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.

Timeline

1. Sep 15, 2026, 2:27 PM UTCCVE published
2. Sep 17, 2026, 2:30 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: partial

3. Sep 17, 2026, 2:30 PM UTCRecord last updated

Affected versions

• tektoncd pipelines-as-code

  fixed in 0.37.8; From 0.38.0 · fixed in 0.39.6; From 0.40.0 · fixed in 0.42.1; From 0.43.0 · fixed in 0.48.0

• github.com/openshift-pipelines/pipelines-as-codeGo

  fixed in 0.37.8; From 0.38.0 · fixed in 0.39.6; From 0.40.0 · fixed in 0.42.1; From 0.43.0 · fixed in 0.48.0

• github.com/openshift-pipelines/pipelines-as-codeGo

  fixed in 0.37.8

• github.com/openshift-pipelines/pipelines-as-codeGo

  From 0.38.0 · fixed in 0.39.6

• github.com/openshift-pipelines/pipelines-as-codeGo

  From 0.40.0 · fixed in 0.42.1

• github.com/openshift-pipelines/pipelines-as-codeGo

  From 0.43.0 · fixed in 0.48.0

References 9