Skip to main content
CVE-2026-54167VulnerabilityPublished Updated

github.com/openshift-pipelines/pipelines-as-code · Pipelines as code: Pipelines-as-Code GitHub App token request can be redirected via untrusted Enterprise Host header

Affects github.com/openshift-pipelines/pipelines-as-codeSource GCVE Database

0
Authoritative record:CVE-2026-54167· High 8.2

Not known to be exploited · CVSS 8.2 High : upgrade to 0.48.0 soon.

Data as of 28 Oct 2026, 17:11 UTC

CVSS 3.1 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.48.0, 0.42.1, 0.39.6 +1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
Gogithub.com/openshift-pipelines/pipelines-as-codeAffected
  • >=0.43.0 <0.48.0
Fixed in
  • 0.48.0
Gogithub.com/openshift-pipelines/pipelines-as-codeAffected
  • >=0.40.0 <0.42.1
Fixed in
  • 0.42.1
Gogithub.com/openshift-pipelines/pipelines-as-codeAffected
  • >=0.38.0 <0.39.6
Fixed in
  • 0.39.6
Gogithub.com/openshift-pipelines/pipelines-as-codeAffected
  • <0.37.8
Fixed in
  • 0.37.8

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in versions 0.48.0, 0.42.1, 0.39.6, and 0.37.8 that addresses this vulnerability by validating webhook signatures before token generation and verifying the Enterprise host. Until patched, operators should block or strip unexpected X-GitHub-Enterprise-Host headers at ingress or proxies, reject such headers for GitHub.com installations, and restrict allowed Enterprise hostnames for GitHub Enterprise Server. Additionally, restrict webhook endpoint access to trusted sources. If exploitation is suspected, rotate the GitHub App private key and review installation token activity.

Description

Pipelines-as-Code versions prior to 0.48.0, 0.42.1, 0.39.6, and 0.37.8 are vulnerable to credential exfiltration via the GitHub App webhook endpoint. The vulnerability arises because the application accepts the X-GitHub-Enterprise-Host header without proper validation before generating GitHub App tokens, allowing an attacker to redirect token requests to a malicious host. This can lead to exposure of the GitHub App JWT, enabling token minting within the JWT validity window. The issue is fixed by validating webhook signatures before token generation and verifying the Enterprise host against the repository URL. Operators are advised to block or strip unexpected headers and restrict webhook endpoint access until patched.

References

Community reviews

Loading reviews…