Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.59% for the current model date.
BlackTreeCVE Intelligencetektoncd · pipelines-as-code
Official source article: GitHub GHSA-6F2P-296R-CC28 ↗. Check the applicable product and release in the original source.
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| Gogithub.com/openshift-pipelines/pipelines-as-code | SEMVER: introduced 0; fixed 0.37.8 | 0.37.8 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Gogithub.com/openshift-pipelines/pipelines-as-code | SEMVER: introduced 0.38.0; fixed 0.39.6 | 0.39.6 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Gogithub.com/openshift-pipelines/pipelines-as-code | SEMVER: introduced 0.40.0; fixed 0.42.1 | 0.42.1 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Gogithub.com/openshift-pipelines/pipelines-as-code | SEMVER: introduced 0.43.0; fixed 0.48.0 | 0.48.0 | OSV record ↗aggregator derived · 10 Sep 2026 |
| gogithub.com/openshift-pipelines/pipelines-as-code | < 0.37.8 | 0.37.8 | GitHub advisory ↗upstream repository advisory · 20 Aug 2026 |
| gogithub.com/openshift-pipelines/pipelines-as-code | >= 0.38.0, < 0.39.6 | 0.39.6 | GitHub advisory ↗upstream repository advisory · 20 Aug 2026 |
| gogithub.com/openshift-pipelines/pipelines-as-code | >= 0.40.0, < 0.42.1 | 0.42.1 | GitHub advisory ↗upstream repository advisory · 20 Aug 2026 |
| gogithub.com/openshift-pipelines/pipelines-as-code | >= 0.43.0, < 0.48.0 | 0.48.0 | GitHub advisory ↗upstream repository advisory · 20 Aug 2026 |
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
The vendor explicitly states that these products are not affected by this CVE.
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Fix not verifiedPipelines-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, a GitHub App installation token created during webhook processing is not scoped to the repository that triggered the event when the App is installed across multiple repositories. A user with push access to one repository can submit a PipelineRun containing a pipelinesascode.tekton.dev/task remote task annotation that targets a private repository in the same installation. When ScopeTokenToListOfRepos returns no explicit scope, the missing triggering repository ID leaves the token able to access the entire installation. Pipelines-as-Code resolves and inlines the remote private task with that token, disclosing the repository's Tekton definitions. The demonstrated impact is read-only and does not provide write access. This issue is fixed in versions 0.37.8, 0.39.6, 0.42.1, and 0.48.0.
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, a GitHub App installation token created during webhook processing is not scoped to the repository that triggered the event when the App is installed across multiple repositories. A user with push access to one repository can submit a PipelineRun containing a pipelinesascode.tekton.dev/task remote task annotation that targets a private repository in the same installation. When ScopeTokenToListOfRepos returns no explicit scope, the missing triggering repository ID leaves the token able to access the entire installation. Pipelines-as-Code resolves and inlines the remote private task with that token, disclosing the repository's Tekton definitions. The demonstrated impact is read-only and does not provide write access. This issue is fixed in versions 0.37.8, 0.39.6, 0.42.1, and 0.48.0.
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
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, a GitHub App installation token created during webhook processing is not scoped to the repository that triggered the event when the App is installed across multiple repositories. A user with push access to one repository can submit a PipelineRun containing a pipelinesascode.tekton.dev/task remote task annotation that targets a private repository in the same installation. When ScopeTokenToListOfRepos returns no explicit scope, the missing triggering repository ID leaves the token able to access the entire installation. Pipelines-as-Code resolves and inlines the remote private task with that token, disclosing the repository's Tekton definitions. The demonstrated impact is read-only and does not provide write access. This issue is fixed in versions 0.37.8, 0.39.6, 0.42.1, and 0.48.0.
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
Operational remediation based on structured source evidence.
Published 15 Sept 2026 · Last source change 17 Sept 2026, 14:30 UTC · CWE-269 · Improper Privilege Management
Core structured fields are present and their contributing authorities are shown above.