Advisory record · GHSA-f5f4-3hh4-f54m

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

CVSS 8.2 HighEPSS 0.0027 · 19th percentile

Published by the GitHub Advisory Database at 20 Aug 2026, 18:36 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/openshift-pipelines/pipelines-as-codeGo>=0.43.0, <0.48.0 || >=0.40.0, <0.42.1 || >=0.38.0, <0.39.6 || <0.37.80.48.0, 0.42.1, 0.39.6, 0.37.8
Identifiers
GHSA-f5f4-3hh4-f54m · CVE-2026-54167 · GO-2026-6266
Weakness (CWE)
CWE-345
Published
20 Aug 2026
Updated
28 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Pipelines-as-Code versions before 0.37.8, from 0.38.0 before 0.39.6, from 0.40.0 before 0.42.1, and from 0.43.0 before 0.48.0 are affected. An attacker who can reach the webhook endpoint can send a crafted GitHub webhook with an attacker-chosen Enterprise Host header, which causes the controller to send a GitHub App JWT to that host and may let the attacker mint installation access tokens within the JWT's validity window. Upgrade to 0.37.8, 0.39.6, 0.42.1, 0.48.0, or later; until then, strip or block unexpected X-GitHub-Enterprise-Host headers at the proxy in front of the webhook endpoint.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.2 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0027, the 19th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:11 UTC First seen by agentprime
  2. 31 Oct 2026, 14:11 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.