LiveActive security incident?Get immediate response
CVE Record

CVE-2026-33211: Tekton Pipelines git resolver has path traversal that allows reading arbitrary files from the resolver pod

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, 1.3.3, 1.6.1, 1.9.2, and 1.10.2 contain a patch.

CriticalCVSS 9.6Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A permitted Tekton tenant can abuse the git resolver to read files from its pod, including Kubernetes ServiceAccount tokens. Those credentials could enable further access according to their assigned permissions. The issue crosses tenant and workload trust boundaries, making rapid remediation important in shared CI/CD environments.

Executive priority

Treat this as an urgent CI/CD platform issue, especially in multi-tenant clusters. Patch promptly, restrict resolver request creation during remediation, and investigate possible token exposure. Priority may be reduced only after confirming no affected version or accessible git resolver exists.

Technical view

CVE-2026-33211 is a CWE-22 path traversal in the git resolver’s `pathInRepo` handling. A user able to create ResolutionRequests, directly or through qualifying TaskRuns or PipelineRuns, can retrieve arbitrary resolver-pod files. Contents appear base64-encoded in `resolutionrequest.status.data`. CVSS 3.1 is 9.6: network-accessible, low complexity, low privileges, no interaction, and changed scope.

Likely exposure

Exposure requires Tekton Pipelines in an affected range, use or availability of the git resolver, and tenant permission to create ResolutionRequests directly or indirectly. Affected ranges are 1.0.0, 1.1.0–1.3.2, 1.4.0–1.6.0, 1.7.0–1.9.1, and 1.10.0–1.10.1.

Exploitation context

The supplied record does not establish active exploitation, and the CVE is not marked as CISA KEV. Exploitation nevertheless requires only low privileges and no user interaction. The immediate capability is file disclosure; theft of ServiceAccount tokens may create follow-on risk depending on token validity and RBAC permissions.

Researcher notes

The important trust boundary is ResolutionRequest creation, including indirect creation through git-resolver TaskRuns or PipelineRuns. Base64 encoding is transport representation, not protection. Assess which identities can read request status and what the resolver ServiceAccount can access. The supplied sources establish the disclosure primitive and patch versions, but not observed attacks.

Mitigation direction

  • Upgrade to 1.0.1, 1.3.3, 1.6.1, 1.9.2, 1.10.2, or a later supported release.
  • Apply relevant Red Hat errata when using affected Red Hat-distributed components.
  • Until upgraded, restrict who can create ResolutionRequests or resolver-backed TaskRuns and PipelineRuns.
  • Rotate resolver-pod ServiceAccount credentials if exploitation is suspected, then review permissions reachable through those credentials.

Validation and detection

  • Inventory deployed Tekton Pipelines versions and compare them with every listed affected range.
  • Confirm whether the git resolver is installed, enabled, or referenced by tenant workloads.
  • Review RBAC for direct and indirect permission to create ResolutionRequests.
  • Audit ResolutionRequests for suspicious `pathInRepo` values and unexpected data returned through status.
  • Check resolver ServiceAccount activity for anomalous API access, then verify upgraded workloads use patched images.
Prepared
Confidence
high
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-33211 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
22Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.6CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N3.15.8GitHub_M
9.6CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N3.15.8redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

9.6Critical
CVSS 3.1 vector shape for CVE-2026-33211Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPTekton Pipelines: github.com/tektoncd/pipeline: Tekton Pipelines: Information disclosure via path traversal in git resolver
other:Red Hat severity ratingcvssV3_1
  • 2026-03-24T00:02:20.093Z: Reported to Red Hat.
  • 2026-03-23T23:55:54.089Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
tektoncdpipeline>= 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.2Listed
Weakness

CWE details

CWE-22

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.