EUVD-2026-24151
GHSA-rmx9-2pp3-xhcr
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Primary rating from GitHub Advisory.
CVSS VectorGitHub Advisory
Lifecycle Timeline
5DescriptionGitHub Advisory
Tekton Pipelines project provides k8s-style resources for declaring CI/CD-style pipelines. From 0.43.0 to 1.11.0, trusted resources verification policies match a resource source string (refSource.URI) against spec.resources[].pattern using regexp.MatchString. In Go, regexp.MatchString reports a match if the pattern matches anywhere in the string, so common unanchored patterns (including examples in tekton documentation) can be bypassed by attacker-controlled source strings that contain the trusted pattern as a substring. This can cause an unintended policy match and change which verification mode/keys apply.
AnalysisAI
Tekton Pipelines 0.43.0 through 1.11.0 allows authenticated attackers to bypass trusted resource verification policies via unanchored regular expression patterns that match substrings rather than exact resource sources, enabling policy manipulation and unauthorized verification mode changes. The vulnerability stems from Go's regexp.MatchString function matching patterns anywhere within a string rather than requiring full anchoring, permitting attackers to craft source URIs containing trusted patterns as substrings to trigger unintended policy matches and potentially apply weaker verification keys or modes.
Technical ContextAI
Tekton Pipelines uses Kubernetes-style resources to declare CI/CD pipelines. The trusted resources verification system enforces security policies by matching a resource source URI (refSource.URI) against configured patterns in spec.resources[].pattern using Go's regexp.MatchString function. The vulnerability arises from a fundamental regex matching semantic: regexp.MatchString returns true if the pattern matches anywhere in the target string, not just at anchored boundaries. Common documentation examples and user-provided patterns typically lack anchors (^ and $), allowing attackers to construct source URIs that contain the trusted pattern as a substring while including additional attacker-controlled content. This causes the verification system to incorrectly match malicious resources against trusted patterns, altering which cryptographic keys or verification modes apply to the resource validation process. The root cause maps to CWE-185 (Incorrect Regular Expression), a classification for regex logic flaws that fail to properly validate input due to improper pattern construction or usage.
RemediationAI
Upgrade Tekton Pipelines to version 1.12.0 or later, which includes the fix for unanchored regex matching in trusted resource verification policies. The upstream fix (GitHub commit b8905600322aa86327baae0a7c04d6cf1207362a) addresses the root cause by properly anchoring regex patterns during verification. There is no workaround available for versions prior to 1.12.0 that remains deployed; however, defenders can implement a compensating control by manually reviewing and explicitly anchoring all patterns in spec.resources[].pattern with ^ and $ delimiters to prevent substring matching. This control has a trade-off: operators must audit and update all existing pipeline policy definitions, a potentially labor-intensive task in large deployments. Additionally, restrict cluster-wide pipeline deployment permissions to trusted administrators only and implement image scanning and provenance verification tools downstream of the pipeline to catch injected unsigned artifacts even if Tekton's verification is bypassed. See the official advisory at https://github.com/tektoncd/pipeline/security/advisories/GHSA-rmx9-2pp3-xhcr for additional context and guidance on policy re-anchoring.
More in Kubernetes
View allA critical vulnerability in Kubernetes ingress-nginx controller allows unauthenticated attackers with pod network access
Credential-harvesting malware compromised 84 versions of 42 TanStack npm packages on 2026-05-11 via chained GitHub Actio
Kubernetes ingress-nginx contains a configuration injection vulnerability via the mirror-target and mirror-host Ingress
A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `auth-url` Ingres
A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `auth-tls-match-c
Kubernetes API server in all versions allow an attacker who is able to create a ClusterIP service and set the spec.exter
A security issue was discovered in Kubernetes where a user that can create pods on Windows nodes may be able to escalate
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Rated critical severity (CVSS 9.9), this vulne
Unauthenticated remote attackers can trigger complete database overwrites, server-side file reads, and SSRF attacks agai
The Kubernetes integration in GitLab Enterprise Edition 11.x before 11.2.8, 11.3.x before 11.3.9, and 11.4.x before 11.4
Fluentd configuration injection in the kube-logging Logging operator before 6.6.0 allows a namespace-scoped user who can
Kyverno Kubernetes policy engine prior to 1.x has a privilege escalation vulnerability (CVSS 9.9) allowing policy bypass
Same weakness CWE-185 – Incorrect Regular Expression
View allSame technique Authentication Bypass
View allVendor StatusVendor
SUSE
Severity: MediumShare
External POC / Exploit Code
Leaving vuln.today