What is the CVSS score of CVE-2026-40161?

CVE-2026-40161 has a CVSS 3.1 base score of 7.7 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N. EPSS exploitation probability: 0.0%.

Which versions of Tekton Pipelines are affected by CVE-2026-40161?

Tekton Pipelines versions 1.0.0-1.10.0 contain a credential leakage vulnerability in the git resolver that allows authenticated cluster users to steal system-configured Git API tokens (GitHub PAT,…. A patch is available.

How to fix or mitigate CVE-2026-40161?

Within 24 hours: Identify all Tekton Pipelines deployments and confirm installed versions (1.0.0-1.10.0 are affected). Within 7 days: (1) Restrict TaskRun and PipelineRun creation privileges to trusted users only via RBAC; (2) audit git resolver configurations for omitted token parameters and enforce explicit token specification; (3) rotate all system-configured Git API tokens. Within 30 days: upgrade Tekton Pipelines to version 1.10.1 or later when released by the vendor; if unavailable, implement network segmentation to restrict resolver egress to approved Git endpoints only.

Tekton Pipelines CVE-2026-40161

EUVD-2026-24165 HIGH

Insertion of Sensitive Information Into Sent Data (CWE-201)

2026-04-21 GitHub_M

GHSA-wjxp-xrpv-xpff

Information Disclosure Kubernetes Gitlab

7.7

CVSS 3.1 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

7.7 HIGH

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

SUSE

HIGH

qualitative

Red Hat

7.7 MEDIUM

qualitative

Primary rating from GitHub Advisory.

CVSS VectorGitHub Advisory

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Re-analysis Queued

Apr 22, 2026 - 21:37 vuln.today

cvss_changed

Analysis Generated

Apr 21, 2026 - 17:34 vuln.today

EUVD ID Assigned

Apr 21, 2026 - 17:00 euvd

EUVD-2026-24165

Analysis Generated

Apr 21, 2026 - 17:00 vuln.today

CVE Published

Apr 21, 2026 - 16:26 nvd

HIGH 7.7

DescriptionGitHub Advisory

Tekton Pipelines project provides k8s-style resources for declaring CI/CD-style pipelines. From 1.0.0 to 1.10.0, the Tekton Pipelines git resolver in API mode sends the system-configured Git API token to a user-controlled serverURL when the user omits the token parameter. A tenant with TaskRun or PipelineRun create permission can exfiltrate the shared API token (GitHub PAT, GitLab token, etc.) by pointing serverURL to an attacker-controlled endpoint.

AnalysisAI

Credential leakage in Tekton Pipelines git resolver allows authenticated users to exfiltrate system-configured Git API tokens (GitHub PAT, GitLab tokens) by directing the resolver to attacker-controlled endpoints. Affects versions 1.0.0 through 1.10.0 when users omit the token parameter in TaskRun or PipelineRun configurations. CVSS 7.7 with scope change reflects cross-tenant credential theft potential in multi-tenant Kubernetes environments. No active exploitation confirmed (not in CISA KEV), but exploitation is straightforward for authenticated cluster users with TaskRun/PipelineRun creation privileges.

Technical ContextAI

Tekton Pipelines is a Kubernetes-native CI/CD framework that extends Kubernetes with custom resource definitions for pipeline orchestration. The git resolver component operates in API mode to fetch pipeline definitions from Git repositories using configured authentication tokens. The vulnerability stems from insecure credential handling (CWE-201: Insertion of Sensitive Information Into Sent Data) where the resolver automatically attaches system-level Git credentials (GitHub Personal Access Tokens, GitLab API tokens) to requests when users specify a custom serverURL but omit explicit token parameters. This design flaw violates the principle of least privilege by allowing tenant-level users to redirect authenticated requests to arbitrary endpoints. The scope change (S:C) in the CVSS vector reflects the cross-tenant impact - an attacker with low privileges in one tenant can steal credentials that may provide broader system access beyond their original authorization boundary.

RemediationAI

Upgrade to Tekton Pipelines version 1.10.1 or later, which addresses the credential leakage by validating serverURL against configured Git hosts before attaching authentication tokens. Until patching, implement compensating controls: (1) Remove system-level Git API tokens from Tekton configuration and require users to provide explicit tokens in TaskRun/PipelineRun definitions - this eliminates the vulnerable credential pool but breaks workflows assuming automatic authentication; (2) Use Kubernetes RBAC to restrict TaskRun/PipelineRun creation to highly trusted users only - reduces attack surface but may conflict with CI/CD automation requirements; (3) Deploy network policies blocking egress from Tekton resolver pods to untrusted destinations - requires comprehensive allowlist of legitimate Git hosting endpoints and may interfere with private Git servers. Consult GitHub advisory GHSA-wjxp-xrpv-xpff for vendor-recommended migration path. After upgrading, audit Git API token permissions and rotate any tokens potentially exposed during the vulnerable period.