CVE-2026-54167
HIGHCVE-2026-54167 is a high-severity (CVSS 8.2) vulnerability in github.com/openshift-pipelines/pipelines-as-code. O3 Security confirms whether CVE-2026-54167 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Pipelines-as-Code GitHub App token request can be redirected via untrusted Enterprise Host header
Real-World Exposure
github.com/openshift-pipelines/pipelines-as-code🐹github.com/openshift-pipelines/pipelines-as-code🐹github.com/openshift-pipelines/pipelines-as-code🐹github.com/openshift-pipelines/pipelines-as-codeReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
Pipelines-as-Code installations using the GitHub App provider are vulnerable to GitHub App credential exfiltration through the webhook endpoint.
Affected versions accepted the X-GitHub-Enterprise-Host request header as the GitHub Enterprise API host during GitHub App token generation. For GitHub webhook events containing an installation.id, Pipelines-as-Code generated a GitHub App JWT and requested an installation access token before validating the webhook signature or checking that the Enterprise host matched the repository URL in the signed payload.
An attacker who can reach the Pipelines-as-Code webhook endpoint can send a crafted GitHub webhook payload containing an installation ID and set X-GitHub-Enterprise-Host to an attacker-controlled host. During token generation, the controller signs a GitHub App JWT locally and sends it to the selected API host. This can disclose the GitHub App JWT to the attacker-controlled service, allowing the attacker to attempt to mint GitHub App installation access tokens within the JWT validity window, subject to the GitHub App installation and permissions.
The incoming webhook flow also trusted X-GitHub-Enterprise-Host during GitHub App installation lookup and token generation. In that path, exploitation requires a valid incoming webhook secret for the target Repository CR.
Patches
The fix validates the webhook signature before GitHub App token generation, verifies that X-GitHub-Enterprise-Host matches the repository URL in the webhook payload, and stops using the request header to select the GitHub Enterprise host for incoming webhook token requests. For incoming webhooks, the Enterprise host is derived from the configured Repository URL instead.
The fix is available in v0.48.0. Supported backport releases will be added here after release tags are published.
Workarounds
Until a patched release is deployed, operators should block or strip unexpected X-GitHub-Enterprise-Host headers at the ingress or proxy in front of the Pipelines-as-Code webhook endpoint. For GitHub.com installations, reject requests that include this header. For GitHub Enterprise Server installations, allow only the expected Enterprise hostname.
Operators should also restrict access to the webhook endpoint to trusted Git provider sources where possible. If exploitation is suspected, rotate the GitHub App private key and review GitHub App installation token activity.
Credits
Reported and fixed by the Pipelines-as-Code maintainers.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/openshift-pipelines/pipelines-as-code | ≥ 0.43.0&&< 0.48.0 | 0.48.0 |
| 🐹Go | github.com/openshift-pipelines/pipelines-as-code | ≥ 0.40.0&&< 0.42.1 | 0.42.1 |
| 🐹Go | github.com/openshift-pipelines/pipelines-as-code | ≥ 0.38.0&&< 0.39.6 | 0.39.6 |
| 🐹Go | github.com/openshift-pipelines/pipelines-as-code | all versions | 0.37.8 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/openshift-pipelines/pipelines-as-code. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/openshift-pipelines/pipelines-as-code to 0.48.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-54167 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-54167 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-54167. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-54167 in your dependencies?
O3 detects CVE-2026-54167 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.