Vulnerability in github.com/tektoncd/pipeline (CVE-2026-40161)
Summary
Vulnerability in github.com/tektoncd/pipeline (CVE-2026-40161). Confidential information can be exposed externally. Mitigation: upgrade to 1.0.2, 1.3.4, 1.6.2, 1.9.3, 1.11.1 or later.
Original description
The description as published by the source.
Tekton Pipelines project provides k8s-style resources for declaring CI/CD-style pipelines. Starting in version 1.0.0 and prior to versions 1.0.2, 1.3.4, 1.6.2, 1.9.3, and 1.11.1, 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. Versions 1.0.2, 1.3.4, 1.6.2, 1.9.3, and 1.11.1 fix the issue.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-40161 has been found in github.com/tektoncd/pipeline.
Confidential information can be exposed externally. CVSS score: 7.7/10.
What to do: upgrade github.com/tektoncd/pipeline to 1.0.2, 1.3.4, 1.6.2, 1.9.3, 1.11.1 or later.
If unsure, ask your IT team or search "github.com/tektoncd/pipeline CVE-2026-40161" on the vendor's site.
CVE-2026-40161 (github.com/tektoncd/pipeline) — CWE-201 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.0.2, 1.3.4, 1.6.2, 1.9.3, 1.11.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-201) exists in github.com/tektoncd/pipeline.
Check the vendor advisory for the affected versions of github.com/tektoncd/pipeline.
Severity: High (CVSS 7.7/10). Confidential information can be exposed externally.
Update to 1.0.2, 1.3.4, 1.6.2, 1.9.3, 1.11.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/tektoncd/pipeline' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/tektoncd/pipeline' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/tektoncd/pipelineを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/tektoncd/pipeline to 1.0.2, 1.3.4, 1.6.2, 1.9.3, 1.11.1ステージング環境で 1.0.2, 1.3.4, 1.6.2, 1.9.3, 1.11.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- report github.com
- report github.com
- web github.com