NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

CVE-2026-54167: Pipelines-as-Code GitHub App token request can be redirected via untrusted Enterprise Host header

highCVSS 3.1 8.2GHSA-f5f4-3hh4-f54m

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.

Published Aug 20, 2026 · Updated Oct 28, 2026

Affected packages

github.com/openshift-pipelines/pipelines-as-code

Ecosystem
Go
Affected
>= 0.43.0, < 0.48.0
Fixed in
0.48.0
Check
go list -m github.com/openshift-pipelines/pipelines-as-code

github.com/openshift-pipelines/pipelines-as-code

Ecosystem
Go
Affected
>= 0.40.0, < 0.42.1
Fixed in
0.42.1
Check
go list -m github.com/openshift-pipelines/pipelines-as-code

github.com/openshift-pipelines/pipelines-as-code

Ecosystem
Go
Affected
>= 0.38.0, < 0.39.6
Fixed in
0.39.6
Check
go list -m github.com/openshift-pipelines/pipelines-as-code

github.com/openshift-pipelines/pipelines-as-code

Ecosystem
Go
Affected
< 0.37.8
Fixed in
0.37.8
Check
go list -m github.com/openshift-pipelines/pipelines-as-code

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

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.

Credited to ranjiGT.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Go vulnerabilities

All Go entries