Vulnerabilities in pkg:golang/github.com/openshift-pipelines/pipelines-as-code

PACKAGE
Advisory Identifier: GHSA-6f2p-296r-cc28
Advisory Summary

CVE-2026-54168 is a MODERATE (CVSS 6.5) unscoped github app installation token vulnerability (CWE-269: Improper Privilege Management) affecting Tekton Pipelines-as-Code libraries in the Go ecosystem. The issue involves unscoped github app installation token allows unauthorized access to private repositories via remote task resolution. Remediation is available by upgrading affected packages to version 0.37.8, 0.39.6, 0.42.1, 0.48.0.

2 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:golang/github.com/openshift-pipelines/pipelines-as-code

2 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:golang/github.com/openshift-pipelines/pipelines-as-code. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-6f2p-296r-cc28 CVE-2026-54168 MODERATE Tekton Pipelines-as-Code: Unscoped GitHub App installation token allows unauthorized access to private repositories via remote task resolution
GHSA-f5f4-3hh4-f54m CVE-2026-54167 HIGH Pipelines-as-Code GitHub App token request can be redirected via untrusted Enterprise Host header

CVE-2026-54168 at a Glance

CVE Identifier CVE-2026-54168
GHSA Identifier GHSA-6f2p-296r-cc28
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-269: Improper Privilege Management
Affected Product Tekton Pipelines-as-Code
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 6.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-54168

To remediate this vulnerability, upgrade all affected Tekton Pipelines-as-Code dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/openshift-pipelines/pipelines-as-code fixed: 0.37.8
Upgrade github.com/openshift-pipelines/pipelines-as-code to 0.37.8
github.com/openshift-pipelines/pipelines-as-code fixed: 0.39.6
Upgrade github.com/openshift-pipelines/pipelines-as-code to 0.39.6
github.com/openshift-pipelines/pipelines-as-code fixed: 0.42.1
Upgrade github.com/openshift-pipelines/pipelines-as-code to 0.42.1
github.com/openshift-pipelines/pipelines-as-code fixed: 0.48.0
Upgrade github.com/openshift-pipelines/pipelines-as-code to 0.48.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/openshift-pipelines/pipelines-as-code

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-54168, inspect your project dependencies for Tekton Pipelines-as-Code:

inspect dependencies for github.com/openshift-pipelines/pipelines-as-code

Analyze the terminal output to locate any version of Tekton Pipelines-as-Code in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.37.8), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-269: Improper Privilege Management, where the product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. In Tekton Pipelines-as-Code, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact When Pipelines-as-Code is configured with a GitHub App installed across multiple repositories, the installation token issued during webhook processing is not scoped to the triggering repository by default. The token retains access to all repositories in the GitHub App installation. This allows a user with push access to any repository in the installation to craft a PipelineRun with a remote task annotation pointing at a private repository in the same installation: ``` pipelinesascode.tekton.dev/task: "https://github.com/org/private-repo/blob/main/.tekton/secret-task.yaml" ``` Pipelines-as-Code resolves and inlines the remote task using the unscoped token, exposing the contents of the private repository's Tekton definitions. This is a read-only confidentiality breach, no write access is exposed. ### Patches The fix extracts the repository ID from the webhook payload during initial parsing so that it is available for later use. It then adds a fallback in the client setup path so that when no explicit scoping configuration is present and `ScopeTokenToListOfRepos` returns empty, the token is re-issued scoped to the triggering repository's ID rather than retaining access to the entire installation. The initial token remains unscoped so that the extra-repos lookup can still discover and resolve additional repositories when configured. The fix is available in v0.48.0. Supported backport releases will be added here after release tags are published. ### Workarounds Limit the GitHub App installation to only the repositories that require Pipelines-as-Code. Avoid org-wide installations or mixed-trust installations where repositories with different access requirements share the same GitHub App. This restricts the blast radius of the unscoped token to only the repositories that are explicitly selected during App installation. ### Credits Reported and fixed by the Pipelines-as-Code maintainers.

CVE-2026-54168 Affected Tekton Pipelines-as-Code Versions

4 component(s)
Fixed Versions:
0.37.80.39.60.42.10.48.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/openshift-pipelines/pipelines-as-code
Go
< 0.37.8
0.37.8
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.40.0
< 0.42.1
0.42.1
github.com/openshift-pipelines/pipelines-as-code
Go
≥ 0.43.0
< 0.48.0
0.48.0

References

Frequently Asked Questions

What is CVE-2026-54168?
CVE-2026-54168 is a security vulnerability in Tekton Pipelines-as-Code involving Unscoped GitHub App installation token allows unauthorized access to private repositories via remote task resolution under CWE-269: Improper Privilege Management.
Which Tekton Pipelines-as-Code versions are affected?
Affected versions include releases prior to 0.37.8, 0.39.6, 0.42.1, 0.48.0 across affected packages: github.com/openshift-pipelines/pipelines-as-code.
What version fixes CVE-2026-54168?
Upgrading to 0.37.8, 0.39.6, 0.42.1, 0.48.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/openshift-pipelines/pipelines-as-code affected?
Yes, github.com/openshift-pipelines/pipelines-as-code is affected in releases prior to 0.37.8, 0.39.6, 0.42.1, 0.48.0. Upgrade your dependency to 0.37.8, 0.39.6, 0.42.1, 0.48.0 or later.
What is the CVSS score of CVE-2026-54168?
CVE-2026-54168 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-54168?
CVE-2026-54168 is classified under CWE-269: Improper Privilege Management (The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.).
How can I check Go dependencies for CVE-2026-54168?
Run the dependency tree command: 'inspect dependencies for github.com/openshift-pipelines/pipelines-as-code'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-6f2p-296r-cc28",
  "modified" : "2026-08-20T18:36:41Z",
  "published" : "2026-08-20T18:36:40Z",
  "aliases" : [ "CVE-2026-54168" ],
  "summary" : "Tekton Pipelines-as-Code: Unscoped GitHub App installation token allows unauthorized access to private repositories via remote task resolution",
  "details" : "### Impact\nWhen Pipelines-as-Code is configured with a GitHub App installed across multiple repositories, the installation token issued during webhook processing is not scoped to the triggering repository by default. The token retains access to all repositories in the GitHub App installation.\n\nThis allows a user with push access to any repository in the installation to craft a PipelineRun with a remote task annotation pointing at a private repository in the same installation:\n```\npipelinesascode.tekton.dev/task: \"https://github.com/org/private-repo/blob/main/.tekton/secret-task.yaml\"\n```\nPipelines-as-Code resolves and inlines the remote task using the unscoped token, exposing the contents of the private repository's Tekton definitions. This is a read-only confidentiality breach, no write access is exposed.\n\n### Patches\nThe fix extracts the repository ID from the webhook payload during initial parsing so that it is available for later use. It then adds a fallback in the client setup path so that when no explicit scoping configuration is present and `ScopeTokenToListOfRepos` returns empty, the token is re-issued scoped to the triggering repository's ID rather than retaining access to the entire installation. The initial token remains unscoped so that the extra-repos lookup can still discover and resolve additional repositories when configured.\n\nThe fix is available in v0.48.0. Supported backport releases will be added here after release tags are published.\n\n### Workarounds\nLimit the GitHub App installation to only the repositories that require Pipelines-as-Code. Avoid org-wide installations or mixed-trust installations where repositories with different access requirements share the same GitHub App. This restricts the blast radius of the unscoped token to only the repositories that are explicitly selected during App installation.\n\n### Credits\nReported and fixed by the Pipelines-as-Code maintainers.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/openshift-pipelines/pipelines-as-code"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.37.8"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/openshift-pipelines/pipelines-as-code"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.38.0"
      }, {
        "fixed" : "0.39.6"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/openshift-pipelines/pipelines-as-code"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.40.0"
      }, {
        "fixed" : "0.42.1"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/openshift-pipelines/pipelines-as-code"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.43.0"
      }, {
        "fixed" : "0.48.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/tektoncd/pipelines-as-code/security/advisories/GHSA-6f2p-296r-cc28"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/tektoncd/pipelines-as-code"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-269", "CWE-862" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-20T18:36:40Z",
    "nvd_published_at" : null
  }
}