Live › vulnerability › CVE-2026-54167
Go to dashboardPipelines-as-Code sent a GitHub App JWT to an API host taken from an attacker-controlled X-GitHub-Enterprise-Host header, before verifying the webhook signature. An attacker who can reach the webhook endpoint can leak the JWT and try to mint installation access tokens within its validity window.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 15:34 UTC, 0h before NVD. All times on this page are UTC.
Teams running Pipelines-as-Code with the GitHub App provider, where the webhook endpoint is reachable from the internet or an untrusted network. The flaw sits in the token generation path for incoming GitHub webhook events that include an installation ID. Installations on other providers or with the webhook endpoint restricted to trusted sources are less exposed.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| github.com/openshift-pipelines/pipelines-as-code | go | >= 0.43.0, < 0.48.0 | 0.48.0 |
| github.com/openshift-pipelines/pipelines-as-code | go | >= 0.40.0, < 0.42.1 | 0.42.1 |
| github.com/openshift-pipelines/pipelines-as-code | go | >= 0.38.0, < 0.39.6 | 0.39.6 |
| github.com/openshift-pipelines/pipelines-as-code | go | < 0.37.8 | 0.37.8 |
pipelines-as-code controller version; affected if below 0.48.0, 0.42.1 (for 0.40.0 to 0.42.0), 0.39.6 (for 0.38.0 to 0.39.5), or 0.37.8 (for earlier releases)0.48.0, or 0.42.1, 0.39.6, or 0.37.8 on the matching release lineEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
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.
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.
Reported and fixed by the Pipelines-as-Code maintainers.
This page as .md · .json · in your agent: get_signal("CVE-2026-54167")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.