Skip to content

[v0.33.x] Fix CVE-2026-33211: tektoncd/pipeline git resolver path traversal#2015

Merged
khrm merged 1 commit intotektoncd:release-v0.33.xfrom
khrm:pipelinesL33
May 6, 2026
Merged

[v0.33.x] Fix CVE-2026-33211: tektoncd/pipeline git resolver path traversal#2015
khrm merged 1 commit intotektoncd:release-v0.33.xfrom
khrm:pipelinesL33

Conversation

@khrm
Copy link
Copy Markdown
Contributor

@khrm khrm commented May 6, 2026

Bump github.com/tektoncd/pipeline to v1.3.3 which patches a path traversal vulnerability in the git resolver that allowed reading arbitrary files from the resolver pod.

Changes

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

  • Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
  • Has Tests included if any functionality added or changed
  • Follows the commit message standard
  • Meets the Tekton contributor standards (including functionality, content, code)
  • Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
  • Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
  • Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

Bump github.com/tektoncd/pipeline to v1.3.3 which patches a path traversal vulnerability in the git resolver that allowed reading arbitrary files from the resolver pod.
@tekton-robot tekton-robot added the release-note-none Denotes a PR that doesnt merit a release note. label May 6, 2026
@tekton-robot tekton-robot requested review from dibyom and iancoffey May 6, 2026 06:47
@tekton-robot tekton-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label May 6, 2026
Copy link
Copy Markdown
Contributor Author

@khrm khrm left a comment

Choose a reason for hiding this comment

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

/kind security

@tekton-robot tekton-robot added the kind/security Categorizes issue or PR as related to a security issue label May 6, 2026
@khrm khrm changed the title Fix CVE-2026-33211: tektoncd/pipeline git resolver path traversal [v0.33.x] Fix CVE-2026-33211: tektoncd/pipeline git resolver path traversal May 6, 2026
Copy link
Copy Markdown
Contributor Author

@khrm khrm left a comment

Choose a reason for hiding this comment

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

/approve

@tekton-robot
Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: khrm

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 6, 2026
@khrm khrm added the lgtm Indicates that a PR is ready to be merged. label May 6, 2026
@khrm khrm merged commit 93850c7 into tektoncd:release-v0.33.x May 6, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/security Categorizes issue or PR as related to a security issue lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants