CVE-2026-54168

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 65% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
35%
KEV
Not listed

Published

August 20, 2026

Last Modified

September 17, 2026

Advisory Details (9)

Auto-updated Sep 15, 2026
Patch available. Sources: github_release, github, github_commit.
github_release Patch Available

v0.48.0

Patch available: tektoncd/pipelines-as-code v0.48.0

https://github.com/tektoncd/pipelines-as-code/releases/tag/v0.48.0
github_release Patch Available

v0.42.1

Patch available: tektoncd/pipelines-as-code v0.42.1

https://github.com/tektoncd/pipelines-as-code/releases/tag/v0.42.1
github_release Patch Available

v0.39.6

Patch available: tektoncd/pipelines-as-code v0.39.6

https://github.com/tektoncd/pipelines-as-code/releases/tag/v0.39.6
github_release Patch Available

v0.37.8

Patch available: tektoncd/pipelines-as-code v0.37.8

https://github.com/tektoncd/pipelines-as-code/releases/tag/v0.37.8
github_commit

commit e0c4a11ea380 (tektoncd/pipelines-as-code)

Fix landed in tektoncd/pipelines-as-code commit e0c4a11ea380 — awaiting tagged release

https://github.com/tektoncd/pipelines-as-code/commit/e0c4a11ea3800ab9d26cf3a8ae92b74cf18527c3
github_commit

commit ac6fded6dfb6 (tektoncd/pipelines-as-code)

Fix landed in tektoncd/pipelines-as-code commit ac6fded6dfb6 — awaiting tagged release

https://github.com/tektoncd/pipelines-as-code/commit/ac6fded6dfb69ade7197d4eeed6e90ddbe1b79bc
github_commit

commit 40813976a779 (tektoncd/pipelines-as-code)

Fix landed in tektoncd/pipelines-as-code commit 40813976a779 — awaiting tagged release

https://github.com/tektoncd/pipelines-as-code/commit/40813976a77920feaf52671320d6d3c5ff08eb7e
github_commit

commit 001782829e82 (tektoncd/pipelines-as-code)

Fix landed in tektoncd/pipelines-as-code commit 001782829e82 — awaiting tagged release

https://github.com/tektoncd/pipelines-as-code/commit/001782829e82b83ecb3da903f5a024ca0826b64c
github Patch Available

Unscoped GitHub App installation token allows unauthorized access to private repositories via remote task resolution · Advisory · tektoncd/pipelines-as-code · GitHub

https://github.com/tektoncd/pipelines-as-code/security/advisories/GHSA-6f2p-296r-cc28

Vendor Advisories for CVE-2026-54168(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/openshift-pipelines/pipelines-as-code0.48.0

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 9× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 20:18 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 17:54 UTCEG score recompute
  4. 2026-09-17 19:31 UTCEPSS rescore
  5. 2026-09-17 15:30 UTCEG score recompute
  6. 2026-09-17 14:45 UTCEG score recompute
  7. 2026-09-16 19:44 UTCEG score recompute
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-15 15:34 UTCEG score recompute
  10. 2026-08-20 18:42 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-54168?
CVE-2026-54168 is a medium vulnerability published on August 20, 2026. 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…
When was CVE-2026-54168 disclosed?
CVE-2026-54168 was first published in the National Vulnerability Database on August 20, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54168 actively exploited?
CVE-2026-54168 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 64.7% of all scored CVEs.
What is the CVSS score of CVE-2026-54168?
CVE-2026-54168 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-54168?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54168, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54168

Explore →

Is Your Infrastructure Affected by CVE-2026-54168?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.