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

Tekton Pipelines had a flaw in its git resolver that could let an authorized tenant read files from the resolver pod. That may include Kubernetes ServiceAccount tokens. The issue is critical because it can expose sensitive credentials from CI/CD infrastructure, but the supplied sources do not show confirmed active exploitation.

Executive priority

Treat this as urgent for shared CI/CD clusters. The business risk is credential exposure from pipeline infrastructure, which can lead to broader Kubernetes or supply-chain compromise depending on token privileges.

Technical view

CVE-2026-33211 is a CWE-22 path traversal in Tekton Pipelines git resolver pathInRepo handling. A tenant able to create ResolutionRequests, including through TaskRuns or PipelineRuns using the git resolver, can cause arbitrary resolver-pod file reads. Returned file content appears base64-encoded in resolutionrequest.status.data. CVSS is 9.6.

Likely exposure

Exposure is likely limited to Tekton Pipelines deployments in the listed 1.x vulnerable ranges where tenants can create ResolutionRequests, TaskRuns, or PipelineRuns that use the git resolver.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation. The vulnerability requires low-privileged authenticated access, no user interaction, and can cross security scope by exposing files from the resolver pod.

Researcher notes

The key evidence is the advisory’s pathInRepo traversal description, the returned base64 data field, and patched version list. The supplied bundle does not include proof of exploitation, exploit maturity, or complete downstream product impact beyond Red Hat references.

Mitigation direction

  • Upgrade Tekton Pipelines to 1.0.1, 1.3.3, 1.6.1, 1.9.2, or 1.10.2 as applicable.
  • Review the Tekton advisory and relevant Red Hat errata for branch-specific guidance.
  • Restrict who can create ResolutionRequests, TaskRuns, or PipelineRuns using the git resolver.
  • Review and rotate potentially exposed ServiceAccount tokens if suspicious access is identified.

Validation and detection

  • Inventory Tekton Pipelines versions and compare them with the affected version ranges.
  • Identify clusters where the git resolver is enabled and used by tenant workloads.
  • Review RBAC for permissions to create ResolutionRequests, TaskRuns, and PipelineRuns.
  • Inspect ResolutionRequest status data and audit logs for unusual resolver activity.
Prepared
Confidence
high
Sources
12

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.

CWE-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs