CVE-2026-33211 remediation guide

tektoncd pipeline, Builds for Red Hat OpenShift 1.6.0, Red Hat OpenShift Builds 1.7.3

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.1, 1.3.3, 1.6.1, 1.9.2, and 1.10.2, the Tekton Pipelines git resolver is vulnerable to path traversal via the `pathInRepo` parameter. A tenant with permission to create `ResolutionRequests` (e.g. by creating `TaskRuns` or `PipelineRuns` that use the git resolver) can read arbitrary files from the resolver pod's filesystem, including ServiceAccount tokens. The file contents are returned base64-encoded in `resolutionrequest.status.data`. Versions 1.0.1...

Open CVE record

Producttektoncd pipeline, Builds for Red Hat OpenShift 1.6.0, Red Hat OpenShift Builds 1.7.3

Affected versions>= >= 1.0.0, < 1.0.1, >= >= 1.1.0, < 1.3.3, >= >= 1.4.0, < 1.6.1, >= >= 1.7.0, < 1.9.2, >= >= 1.10.0, < 1.10.2, >= 1.1.0 < 1.3.3, >= 1.4.0 < 1.6.1, >= 1.7.0 < 1.9.2, >= 1.10.0 < 1.10.2, 1.0.0

Fixed versions1.3.3, 1.6.1, 1.9.2, 1.10.2

Priority basisReview · CVSS 9.6 · EPSS 0.57%

Identify the affected asset

Confirm whether tektoncd pipeline, Builds for Red Hat OpenShift 1.6.0, Red Hat OpenShift Builds 1.7.3 is installed, record the deployed version and installation path, and identify exposed interfaces.

Record the product name, package or appliance identifier, and installed version.
Identify internet-facing, administrative, API, and internal access paths.
Preserve the pre-change configuration and relevant service logs.

Validate the affected-version match

Compare the deployed version with the affected range: >= >= 1.0.0, < 1.0.1, >= >= 1.1.0, < 1.3.3, >= >= 1.4.0, < 1.6.1, >= >= 1.7.0, < 1.9.2, >= >= 1.10.0, < 1.10.2, >= 1.1.0 < 1.3.3, >= 1.4.0 < 1.6.1, >= 1.7.0 < 1.9.2, >= 1.10.0 < 1.10.2, 1.0.0. Treat incomplete inventory results as unresolved.

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 1.3.3, 1.6.1, 1.9.2, 1.10.2. Preserve configuration and rollback material before change.

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

Confirm the expected version and package state.
Run a functional health check for critical service paths.
Review authentication, error, application, and security monitoring logs.
Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.