CVE-2026-54167: tektoncd pipelines-as-code · Insufficient Verification of Data Authenticity
Affects tektoncd pipelines-as-codeSource CVE Database V5
Not known to be exploited · CVSS 8.2 High · fixed in 0.48.0 : patch tektoncd pipelines-as-code soon.
Data as of 30 Oct 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 19% 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:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 30 Oct 2026.
What to do
Upgrade pipelines-as-code and tektoncd/pipelines-as-code to 0.48.0, 0.42.1, 0.39.6 or 0.37.8.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| tektoncdpipelines-as-code | Affected
| Fixed in
|
| tektoncdpipelines-as-code | Affected
| Fixed in
|
| tektoncdpipelines-as-code | Affected
| Fixed in
|
| tektoncdpipelines-as-code | Affected
| Fixed in
|
GitHubtektoncd/pipelines-as-codepkg:github/tektoncd/pipelines-as-codeOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in Tekton Pipelines-as-Code versions 0.37.8, 0.39.6, 0.42.1, and 0.48.0. Users should upgrade to one of these versions or later to remediate the issue. No other mitigation steps are indicated by the vendor advisory.
Description
Pipelines-as-Code is a CI/CD system that lets users define Tekton pipelines in source code repositories. Prior to 0.37.8, 0.39.6, 0.42.1, and 0.48.0, the GitHub App provider accepts X-GitHub-Enterprise-Host as the API host while processing webhook events containing an installation.id, before webhook signature validation or confirmation that the host matches the repository URL in the signed payload. An unauthenticated attacker who can reach the webhook endpoint can select an attacker-controlled host and cause the controller to send a locally signed GitHub App JWT to that service. The exposed JWT may be used to attempt to mint installation access tokens during its validity window, subject to the GitHub App installation and permissions. The incoming webhook installation-lookup path is also affected, but exploitation of that path requires the valid incoming webhook secret for the target Repository CR. This issue is fixed in versions 0.37.8, 0.39.6, 0.42.1, and 0.48.0.
References
- github.com/tektoncd/pipelines-as-code/security/advisories/GHSA-f5f4-3hh4-f54m (opens in a new tab)
- github.com/tektoncd/pipelines-as-code/commit/402d5c7eeece881cb082ec68e9e8b61709e39ace (opens in a new tab)
- github.com/tektoncd/pipelines-as-code/commit/40813976a77920feaf52671320d6d3c5ff08eb7e (opens in a new tab)
- github.com/tektoncd/pipelines-as-code/commit/ac6fded6dfb69ade7197d4eeed6e90ddbe1b79bc (opens in a new tab)
- github.com/tektoncd/pipelines-as-code/commit/e0c4a11ea3800ab9d26cf3a8ae92b74cf18527c3 (opens in a new tab)
- github.com/tektoncd/pipelines-as-code/releases/tag/v0.37.8 (opens in a new tab)
- github.com/tektoncd/pipelines-as-code/releases/tag/v0.39.6 (opens in a new tab)
- github.com/tektoncd/pipelines-as-code/releases/tag/v0.42.1 (opens in a new tab)
- github.com/tektoncd/pipelines-as-code/releases/tag/v0.48.0 (opens in a new tab)