CVE-2026-54167 Pipelines-as-Code GitHub App token request can be redirected via untrusted Enterprise Host header
An attacker can redirect GitHub App token requests to a malicious host via the Enterprise Host header, potentially exposing JWTs for token minting.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-54167?
CVE-2026-54167 is a high-severity server-side request forgery vulnerability in tektoncd pipelines-as-code, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, 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, the GitHub App provider accepts X-GitHub-Enterprise-Host as the API host while processing webhook events containing an installation.id, before webhook signature validation or confirmation that the host matches the repository URL in the signed payload. An unauthenticated attacker who can reach the webhook endpoint can select an attacker-controlled host and cause the controller to send a locally signed GitHub App JWT to that service. The exposed JWT may be used to attempt to mint installation access tokens during its validity window, subject to the GitHub App installation and permissions. The incoming webhook installation-lookup path is also affected, but exploitation of that path requires the valid incoming webhook secret for the target Repository CR. This issue is fixed in versions 0.37.8, 0.39.6, 0.42.1, and 0.48.0.
Weakness: CWE-345
Which versions are affected by CVE-2026-54167?
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-54167?
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 send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-54167 being exploited?
There is no known exploitation of CVE-2026-54167 in the wild and no public exploit code.
Sources
Also known as GHSA-f5f4-3hh4-f54m, GO-2026-6266.