Privilege Escalation in github.com/openshift-pipelines/pipelines-as-code (CVE-2026-54168)
Summary
Vulnerability in github.com/openshift-pipelines/pipelines-as-code (CVE-2026-54168). Confidential information can be exposed externally. Exploitable via ScopeTokenToListOfRepos. Mitigation: upgrade to 0.48.0 or later.
Original description
The description as published by the source.
Tekton Pipelines-as-Code: Unscoped GitHub App installation token allows unauthorized access to private repositories via remote task resolution in github.com/openshift-pipelines/pipelines-as-code
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54168 has been found in github.com/openshift-pipelines/pipelines-as-code.
Attackers can target a specific entry point like ScopeTokenToListOfRepos over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade github.com/openshift-pipelines/pipelines-as-code to 0.48.0 or later.
If unsure, ask your IT team or search "github.com/openshift-pipelines/pipelines-as-code CVE-2026-54168" on the vendor's site.
CVE-2026-54168 (github.com/openshift-pipelines/pipelines-as-code) — CWE-269 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: ScopeTokenToListOfRepos
Patched: 0.48.0 — apply immediately
Workaround: Limit the GitHub App installation to only the repositories that require Pipelines-as-Code.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-269) exists in github.com/openshift-pipelines/pipelines-as-code. Attackers reach the vulnerable code path via ScopeTokenToListOfRepos.
Check the vendor advisory for the affected versions of github.com/openshift-pipelines/pipelines-as-code. Attack surface: ScopeTokenToListOfRepos.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
Update to 0.48.0.
Workaround: Limit the GitHub App installation to only the repositories that require Pipelines-as-Code.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/openshift-pipelines/pipelines-as-code' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/openshift-pipelines/pipelines-as-code' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/openshift-pipelines/pipelines-as-codeを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Limit the GitHub App installation to only the repositories that require Pipelines-as-Code.パッチが適用されるまでの応急処置として、Limit the GitHub App installation to only the repositories that require Pipelines-as-Code. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade github.com/openshift-pipelines/pipelines-as-code to 0.48.0ステージング環境で 0.48.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- web github.com
- web security-advisories@github.com
- web security-advisories@github.com
- web security-advisories@github.com
- web security-advisories@github.com
- web security-advisories@github.com
- web security-advisories@github.com
- web security-advisories@github.com
- web security-advisories@github.com