VulnerabilityPublished 20 Mar 2026

CVE-2026-33022: tektoncd pipeline · Improper Validation of Array Index

Affects tektoncd pipelineSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.5 Medium · fixed in 1.10.2 : update tektoncd pipeline when convenient.

Data as of 31 Oct 2026, 08:20 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.10.2, 1.9.2, 1.6.1 +2

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
tektoncdpipeline	Affected >=1.10.0 <1.10.2	Fixed in 1.10.2
tektoncdpipeline	Affected >=1.7.0 <1.9.2	Fixed in 1.9.2
tektoncdpipeline	Affected >=1.4.0 <1.6.1	Fixed in 1.6.1
tektoncdpipeline	Affected >=1.1.0 <1.3.3	Fixed in 1.3.3
tektoncdpipeline	Affected >=0.60.0 <1.0.1	Fixed in 1.0.1

AI-suggested

Organizations should immediately upgrade Tekton Pipelines to one of the patched versions: 1.0.1, 1.3.3, 1.6.1, 1.9.2, or 1.10.2, depending on their current version. Until upgrade is possible, restrict permissions to create TaskRun and PipelineRun resources to trusted users only, minimizing the risk of malicious or accidental creation of resources with long resolver names. Implement admission controllers or Kubernetes policies to validate and reject TaskRun or PipelineRun resources with .spec.taskRef.resolver or .spec.pipelineRef.resolver strings longer than 30 characters. Monitor controller logs for panic or CrashLoopBackOff states and have procedures to quickly identify and delete offending resources. Review and audit custom resolver naming conventions to ensure names are within safe length limits. Consider isolating Tekton controllers in dedicated namespaces or clusters to limit blast radius. Maintain regular backups of pipeline configurations to facilitate recovery. Engage with Tekton community updates for any further patches or mitigations.

Description

CVE-2026-33022 is a medium severity denial-of-service vulnerability in Tekton Pipelines affecting multiple versions prior to patched releases. It arises from improper validation of array indices when generating deterministic names for TaskRun or PipelineRun resources with custom resolver names longer than 30 characters. This causes the controller to panic due to invalid string slicing, leading to a cluster-wide controller crash and a CrashLoopBackOff state. The impact blocks all CI/CD pipeline reconciliation until the offending resource is manually removed. Built-in resolvers are unaffected, but any custom resolver name exceeding 30 characters triggers the issue. The vulnerability requires authenticated users with permission to create TaskRun or PipelineRun resources but no user interaction beyond resource creation. Fixed versions have been released that properly truncate the resolver name prefix to prevent the panic. Organizations using Tekton Pipelines with custom resolvers should upgrade immediately to avoid disruption.

Impact

This vulnerability can cause a complete denial of service of Tekton Pipelines controllers in Kubernetes clusters, disrupting all CI/CD pipeline executions and automation relying on Tekton. Since the controller crashes and enters a CrashLoopBackOff, no pipeline runs can be processed until the offending resource is deleted or the controller is upgraded. This can severely impact development velocity, continuous integration, and deployment workflows, especially in organizations heavily reliant on Tekton for automation. The impact is cluster-wide, affecting all pipelines managed by the controller. Attackers with permission to create TaskRun or PipelineRun resources can exploit this to cause operational disruption. Although it does not affect confidentiality or integrity directly, the availability impact is significant. Recovery requires manual intervention or patching, which may cause downtime. The vulnerability is particularly critical in environments where Tekton is used as a central CI/CD platform and where custom resolvers are employed.

CWE-129Improper Validation of Array Index (opens in a new tab)
Variant weaknessLikelihood of exploit: HighOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array.
Architecture and Design · Input Validation
Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overflow Buffers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Mar 2026, 19:40 UTC

WeaknessesCWE-129

Technical details

References

Community reviews

Related threats