MediumCVE-2026-33022

    Tekton Pipelines: Controller can panic when setting long resolver names in TaskRun/PipelineRun (CVE-2026-33022)

    Published Sources: Red Hat, BSI, CVE.org, OSV

    What is affected, what to do

    Tekton Pipelines project provides k8s-style resources for declaring CI/CD-style pipelines. Versions 0.60.0 through 1.0.0, 1.1.0 through 1.3.2, 1.4.0 through 1.6.0, 1.7.0 through 1.9.0, 1.10.0, and 1.10.1 have a denial-of-service vulnerability in that allows any user who can create a TaskRun or PipelineRun to crash the controller cluster-wide by setting .spec.taskRef.resolver (or .spec.pipelineRef.resolver) to a string of 31+ characters.

    Update tekton_pipelines to version 1.3.3, OpenShift Pipelines to version 1.21.1.

    Affected
    • Tektoncd Pipeline gte 0.60.0, < 1.0.1..*

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    6.5

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    6.5

    CVSS v3

    Severity Medium on the scale from 0 to 10.

    Source: Red Hat, BSI, CVE.org, OSV

    0.4 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 31.3

    Show all metrics
    Severity
    Medium
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    55.72 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    6.5 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    6.5
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.4 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    31.3
    Elevated — this CVE ranks above at least 10% of all CVEs scored today.
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-129

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    Tekton Pipelines project provides k8s-style resources for declaring CI/CD-style pipelines. Versions 0.60.0 through 1.0.0, 1.1.0 through 1.3.2, 1.4.0 through 1.6.0, 1.7.0 through 1.9.0, 1.10.0, and 1.10.1 have a denial-of-service vulnerability in that allows any user who can create a TaskRun or PipelineRun to crash the controller cluster-wide by setting .spec.taskRef.resolver (or .spec.pipelineRef.resolver) to a string of 31+ characters. The crash occurs because GenerateDeterministicNameFromSpec produces a name exceeding the 63-character DNS-1123 label limit, and its truncation logic panics on a [-1] slice bound since the generated name contains no spaces. Once crashed, the controller enters a CrashLoopBackOff on restart (as it re-reconciles the offending resource), blocking all CI/CD reconciliation until the resource is manually deleted. Built-in resolvers (git, cluster, bundles, hub) are unaffected due to their short names, but any custom resolver name triggers the bug. The fix truncates the resolver-name prefix instead of the full string, preserving the hash suffix for determinism and uniqueness. This issue has been patched in versions 1.0.1, 1.3.3, 1.6.1, 1.9.2 and 1.10.2.

    Source: redhat_csaf, BSI WID Portal, BSI CSAF, NVD (NIST), cvelistv5, OSV (Open Source Vulnerabilities), CVE.org (MITRE)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    tektoncdpipeline
    • ≥ 0.60.0, < 1.0.1
    • —
    linuxfoundationtekton_pipelines
    • 1.1.0 – < 1.3.3
    • 1.10.0 – < 1.10.2
    • 1.4.0 – < 1.6.1
    • 1.7.0 – < 1.9.2
    • 0.60.0 – < 1.0.1
    • 1.3.3
    • 1.10.2
    • 1.6.1
    • 1.9.2
    • 1.0.1
    Red HatOpenShift Pipelines
    • < 1.21.1
    • < 1.20.5
    • < 1.20.4
    • 1.21.1
    • 1.20.5
    • 1.20.4
    gogithub.com/tektoncd/pipeline
    • 0.60.0
    • 1.7.0
    • 1.10.0
    • 1.4.0
    • 1.1.0
    • —
    • —
    • —
    • —
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-129Improper Validation of Array Index

      Variant

      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.

      Entry at MITRE CWE-129

    References & sources

    • github.comtektoncd/pipeline/security/advisories/GHSA-cv4x-93xx-wgfjadvisory, x_refsource_CONFIRM, Patch, Vendor advisory
    • github.comtektoncd/pipeline/commit/5eead3f859b9fix
    • github.comtektoncd/pipeline/commit/01673237c464fix
    • github.comtektoncd/pipeline/commit/edc64bbf2232fix
    • github.comtektoncd/pipeline/commit/0fa2d66cff81fix
    • github.comtektoncd/pipeline/commit/5e4905fb6754fix
    • github.comtektoncd/pipeline/commit/ebc197e2b973fix
    • github.comtektoncd/pipeline/commit/5eead3f859b9f938e86039e4d29185092c1d4e…x_refsource_MISC, Patch
    • NVD (NIST)vuln/detail/CVE-2026-33022advisory
    • github.comtektoncd/pipeline/commit/01673237c464cfac7e286183f5c9e9d6ec951a…web
    • github.comtektoncd/pipeline/commit/0fa2d66cff814838c3a10cce252104c7fe6189…web
    • github.comtektoncd/pipeline/commit/5e4905fb6754efa5ecea54de195738d73fb0e0…web
    • github.comtektoncd/pipeline/commit/ebc197e2b9733deedaa1624212ec66dcdf61ea…web
    • github.comtektoncd/pipeline/commit/edc64bbf22323fcf218170f19047c9bcd8163e…web
    • github.comtektoncd/pipelinepackage
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-33022
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-33022"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-33022.svg?lang=en" alt="CVE-2026-33022 – NEOSEC Intel" height="20"></a>