Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.7

Tekton Pipelines: Git resolver API mode leaks system-configured API token to user-controlled serverURL

CVE-2026-40161GHSA-wjxp-xrpv-xpff

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/tektoncd/pipeline 1.11.1, 1.9.3, 1.6.2, 1.3.4, 1.0.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/tektoncd/pipeline

    Affected
    >= 1.0.0, < 1.0.2>= 1.2.0, < 1.3.4>= 1.4.0, < 1.6.2>= 1.7.0, < 1.9.3>= 1.10.0, < 1.11.1
    Fixed in
    1.0.2, 1.11.1, 1.9.3, 1.6.2, 1.3.4

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
EPSS
  • CVE-2026-40161: 0.26% estimated exploitation activity in the next 30 days; percentile 17.80 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary 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. Details The git resolver's ResolveAPIGit() function in pkg/resolution/resolver/git/resolver.go constructs an SCM client using the user-supplied serverURL and a token obtained via getAPIToken(). When the user provides serverURL but omits the token parameter: 1. getSCMTypeAndServerURL() reads serverURL directly from user params (params[ServerURLParam]) with no validation against the system-configured URL. 2. secretRef is set to nil because the user did not provide a token parameter. 3. getAPIToken(ctx, nil, APISecretNameKey) is called. It detects apiSecret == nil, creates a new secretCacheKey, and populates it from the system-configured…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-wjxp-xrpv-xpff

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-40161

Advisory: Tekton Pipelines: Git resolver API mode leaks system-configured API token to user-controlled serverURL
IDs: CVE-2026-40161, GHSA-wjxp-xrpv-xpff
Record: https://patchnext.com/advisories/cve-2026-40161 (revision 1, source checked 26 Oct 2026, 15:22 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/tektoncd/pipeline 1.11.1, 1.9.3, 1.6.2, 1.3.4, 1.0.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/tektoncd/pipeline: affected >= 1.0.0, < 1.0.2; >= 1.2.0, < 1.3.4; >= 1.4.0, < 1.6.2; >= 1.7.0, < 1.9.3; >= 1.10.0, < 1.11.1; fixed in 1.0.2, 1.11.1, 1.9.3, 1.6.2, 1.3.4

## Suggested inspection (read-only)
- Go github.com/tektoncd/pipeline: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/tektoncd/pipeline.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-wjxp-xrpv-xpff (GitHub-reviewed advisory GHSA-wjxp-xrpv-xpff lists affected ranges: Go github.com/tektoncd/pipeline >=1.0.0 =1.2.0 =1.4.0 =1.7.0 =1.10.0 <1.11.1)

Commands are suggestions: review each one before running it.

Loading voting…