CVE & CISA-KEV Catalog

CVE-2026-54167

HIGH
8.2
CVSS v3
NVD

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.

How to fix

No published remediation has been found for this vulnerability's affected products yet.

Mitigation guidance may be in the linked vendor advisories in the References section below.

TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works

CVSS v3 Vector

Exploitability

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityHigh
IntegrityLow
AvailabilityNone

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Exploit Intelligence

0.18%probability of exploitation in 30 days
8thpercentile

Low risk: more likely to be exploited than 8% of all known CVEs.

References

Related Vulnerabilities

Other CWE-345 vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2023-38831High7.898%KEV + RansomFix
CVE-2016-4553High8.680%-Fix
CVE-2016-4554High8.639%-Fix
CVE-2023-35719Medium6.825%--
CVE-2022-26871Critical9.820%KEV-
CVE-2014-4936High9.317%--

Common questions

How do I fix CVE-2026-54167?

No published fix for CVE-2026-54167 has been found yet. Check the linked vendor advisories for guidance as it becomes available.

Is CVE-2026-54167 being actively exploited?

Not that we know of. CVE-2026-54167 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.18% is the estimated probability that it will be exploited in the next 30 days. That is higher than 8% of all scored CVEs.

How severe is CVE-2026-54167?

CVE-2026-54167 has a CVSS v3 base score of 8.2, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

Embed a live status badge for CVE-2026-54167
CVE-2026-54167 severity badge

Markdown

[![CVE-2026-54167](https://tridentstack.com/cve/badge/CVE-2026-54167.svg)](https://tridentstack.com/cve/CVE-2026-54167)

HTML

<a href="https://tridentstack.com/cve/CVE-2026-54167"><img src="https://tridentstack.com/cve/badge/CVE-2026-54167.svg" alt="CVE-2026-54167"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

See how it worksStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-15.