Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-54167 high CVSS 8.2

Vulnerability in github.com/openshift-pipelines/pipelines-as-code (CVE-2026-54167)

Summary

Vulnerability in github.com/openshift-pipelines/pipelines-as-code (CVE-2026-54167). Confidential information can be exposed externally. Exploitable via installation.id. Mitigation: upgrade to 0.37.8 or later.

Original description

The description as published by the source.

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 repo…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-54167 has been found in github.com/openshift-pipelines/pipelines-as-code.
Attackers can target a specific entry point like installation.id over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.2/10.
What to do: upgrade github.com/openshift-pipelines/pipelines-as-code to 0.37.8 or later.
If unsure, ask your IT team or search "github.com/openshift-pipelines/pipelines-as-code CVE-2026-54167" on the vendor's site.

CVE-2026-54167 (github.com/openshift-pipelines/pipelines-as-code) — CWE-345 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: installation.id
Patched: 0.37.8 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-345) exists in github.com/openshift-pipelines/pipelines-as-code. Attackers reach the vulnerable code path via installation.id without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/openshift-pipelines/pipelines-as-code. Attack surface: installation.id.

🔥 Severity

Severity: High (CVSS 8.2/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 0.37.8.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/openshift-pipelines/pipelines-as-code' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/openshift-pipelines/pipelines-as-code' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/openshift-pipelines/pipelines-as-code を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/openshift-pipelines/pipelines-as-code to 0.37.8

    ステージング環境で 0.37.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/openshift-pipelines/pipelines-as-code
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.37.8"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details