Skip to content

chore(deps): bump tektoncd/pipeline to v1.13.1 to address CVE-2026-33022#2795

Merged
chmouel merged 2 commits into
mainfrom
fix/cve-2026-33022-tektoncd-pipeline-main-attempt-1
Jun 23, 2026
Merged

chore(deps): bump tektoncd/pipeline to v1.13.1 to address CVE-2026-33022#2795
chmouel merged 2 commits into
mainfrom
fix/cve-2026-33022-tektoncd-pipeline-main-attempt-1

Conversation

@theakshaypant

Copy link
Copy Markdown
Member

📝 Description of the Change

Upgrades github.com/tektoncd/pipeline from v1.11.1 → v1.13.1 to address reported
security vulnerabilities flagged by automated scanners (GO-2026-4730 / CVE-2026-33022).

Changes:

  • github.com/tektoncd/pipeline v1.11.1 → v1.13.1
  • github.com/google/cel-go v0.28.0 → v0.28.1 (co-upgrade)
  • github.com/jenkins-x/go-scm v1.15.17 → v1.15.22 (co-upgrade)
  • go.opentelemetry.io/otel v1.43.0 → v1.44.0 (co-upgrade)
  • go.uber.org/zap v1.27.1 → v1.28.0 (co-upgrade)
  • k8s.io/{api,apimachinery,client-go} v0.35.4 → v0.35.5 (co-upgrade)
  • google.golang.org/grpc v1.80.0 → v1.81.1 (co-upgrade)

VEX Analysis

CVE-2026-33022 (GHSA-cv4x-93xx-wgfj, CVSS 6.5 Medium)

  • Tekton Pipelines controller panics when spec.taskRef.resolver is ≥31 chars
  • Fix: GenerateDeterministicNameFromSpec in pkg/resolution/resource/name.go was patched in main (2026-03-11), then backported to v1.10.2, and included from v1.11.1+
  • PAC's relationship: PAC does NOT import pkg/resolution/resource — confirmed by vendor directory which only contains pkg/apis, pkg/client, pkg/reconciler, etc. The vulnerable code path is not compiled into PAC binaries.
  • Upgrade benefit: Moves from v1.11.1 (already fixed) to v1.13.1 (latest) to clear scanner noise and pick up subsequent security improvements.

CVE-2023-37264 (GHSA-w2h3-vvvq-3m53, CVSS 3.7 Low)

  • Pipelines controller does not validate child UIDs — affects cmd/controller binary
  • PAC's relationship: PAC uses tektoncd/pipeline only as a client/API library (pkg/apis/pipeline/v1, pkg/client/clientset/versioned, etc.). PAC does not run or embed the Tekton controller binary.
  • VEX justification: Vulnerable Code not in Execute Path

How this upgrade was done

  1. GOTOOLCHAIN=go1.26.4 go get github.com/tektoncd/pipeline@v1.13.1
  2. GOTOOLCHAIN=go1.26.4 go mod tidy
  3. GOTOOLCHAIN=go1.26.4 go mod vendor
  4. GOTOOLCHAIN=go1.26.4 go build ./...
  5. GOTOOLCHAIN=go1.26.4 go mod verify
  6. GOTOOLCHAIN=go1.26.4 go test ./pkg/...

👨🏻‍💼 Linked Jira

SRVKP-9042

🔗 Linked GitHub Issue

N/A

🧪 Testing Strategy

  • Unit tests — all passed (go test ./pkg/...)
  • Integration tests
  • End-to-end tests
  • Manual testing

Validation run locally:

  • GOTOOLCHAIN=go1.26.4 go build ./... — success, no errors
  • GOTOOLCHAIN=go1.26.4 go mod verify — all modules verified
  • GOTOOLCHAIN=go1.26.4 go test ./pkg/... — all 22 test packages passed

🤖 AI Assistance

Generated by CVE Fixer Workflow (Ambient Code Platform)

@linux-foundation-easycla

linux-foundation-easycla Bot commented Jun 22, 2026

Copy link
Copy Markdown

CLA Signed
The committers listed above are authorized under a signed CLA.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates several Go dependencies in go.mod and go.sum, including github.com/google/cel-go, github.com/jenkins-x/go-scm, github.com/tektoncd/pipeline, go.opentelemetry.io/otel, go.uber.org/zap, and various Kubernetes (k8s.io) libraries to their newer versions. I have no feedback to provide as there are no review comments.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

@codecov

codecov Bot commented Jun 22, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 0% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 59.77%. Comparing base (3dcf4ae) to head (5e686e4).

Files with missing lines Patch % Lines
pkg/test/tracing/tracing.go 0.00% 1 Missing ⚠️
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2795   +/-   ##
=======================================
  Coverage   59.77%   59.77%           
=======================================
  Files         210      210           
  Lines       21135    21135           
=======================================
  Hits        12633    12633           
  Misses       7707     7707           
  Partials      795      795           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

theakshaypant and others added 2 commits June 22, 2026 14:12
- Update github.com/tektoncd/pipeline from v1.11.1 to v1.13.1
- Co-upgrades: cel-go v0.28.1, go-scm v1.15.22, otel v1.44.0,
  zap v1.28.0, k8s.io/* v0.35.5, grpc v1.81.1

CVE-2026-33022 (GHSA-cv4x-93xx-wgfj, CVSS 6.5 Medium):
Tekton Pipelines controller panic via long resolver name in
GenerateDeterministicNameFromSpec. A user with TaskRun/PipelineRun
create access can crash the Pipelines controller into CrashLoopBackOff.
Fixed in upstream tektoncd/pipeline v1.10.2+ and v1.11.1+ (fix
backported via sanitizedName).

Note: CVE-2023-37264 (GO-2023-1901) affects cmd/controller only; PAC
uses only the library APIs (pkg/apis, pkg/client) and does not run the
Tekton controller binary.

Resolves: SRVKP-9042

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: Akshay Pant <akpant@redhat.com>
Value.Emit() is deprecated in the updated OpenTelemetry SDK;
replace with Value.String() to resolve linter warning.

Signed-off-by: Akshay Pant <akpant@redhat.com>
@theakshaypant theakshaypant force-pushed the fix/cve-2026-33022-tektoncd-pipeline-main-attempt-1 branch from 9687ff9 to 5e686e4 Compare June 22, 2026 08:45
@chmouel chmouel merged commit 20a29a9 into main Jun 23, 2026
24 of 25 checks passed
@chmouel chmouel deleted the fix/cve-2026-33022-tektoncd-pipeline-main-attempt-1 branch June 23, 2026 07:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants