CVE-2026-54168 Tekton Pipelines-as-Code: Unscoped GitHub App installation token allows unauthorized access to private repositories via remote task resolution
Attackers with push access to one repository can read private Tekton definitions from other repositories in the same GitHub App installation due to unscoped tokens.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-54168?
CVE-2026-54168 is a medium-severity missing authorization vulnerability in tektoncd pipelines-as-code, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Which versions are affected by CVE-2026-54168?
9 open source packages ship an affected version, including github.com/openshift-pipelines/pipelines-as-code.
| Package | Affected | Fixed in |
|---|---|---|
github.com/openshift-pipelines/pipelines-as-code Go | All versions | 0.37.8, 0.39.6, 0.42.1, 0.48.0 |
github.com/openshift-pipelines/pipelines-as-code Go | All versions | 0.37.8 |
github.com/openshift-pipelines/pipelines-as-code Go | All versions | 0.37.8 |
github.com/openshift-pipelines/pipelines-as-code Go | From 0.38.0 | 0.39.6 |
github.com/openshift-pipelines/pipelines-as-code Go | From 0.38.0 | 0.39.6 |
github.com/openshift-pipelines/pipelines-as-code Go | From 0.40.0 | 0.42.1 |
3 more packages
github.com/openshift-pipelines/pipelines-as-code Go | From 0.40.0 | 0.42.1 |
github.com/openshift-pipelines/pipelines-as-code Go | From 0.43.0 | 0.48.0 |
github.com/openshift-pipelines/pipelines-as-code Go | From 0.43.0 | 0.48.0 |
How do I fix CVE-2026-54168?
Upgrade github.com/openshift-pipelines/pipelines-as-code to a fixed version for your release line: 0.37.8, 0.39.6, 0.42.1 or 0.48.0.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-54168 being exploited?
There is no known exploitation of CVE-2026-54168 in the wild and no public exploit code.
Sources
Also known as GHSA-6f2p-296r-cc28, GO-2026-6263.