Advisory record · GHSA-rmx9-2pp3-xhcr

Tekton Pipelines has VerificationPolicy regex pattern bypass via substring matching

CVSS 6.5 MediumEPSS 0.0026 · 18th percentile

Published by the GitHub Advisory Database at 21 Apr 2026, 16:25 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/tektoncd/pipelineGo>=0.43.0, <1.0.2 || >=1.2.0, <1.3.4 || >=1.4.0, <1.6.2 || >=1.7.0, <1.9.3 || >=1.10.0, <1.11.11.0.2, 1.3.4, 1.6.2, 1.9.3, 1.11.1
Identifiers
GHSA-rmx9-2pp3-xhcr · CVE-2026-25542 · GO-2026-5630
Weakness (CWE)
CWE-185
Published
21 Apr 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Tekton Pipelines versions >=0.43.0 before 1.0.2, >=1.2.0 before 1.3.4, >=1.4.0 before 1.6.2, >=1.7.0 before 1.9.3, and >=1.10.0 before 1.11.1 are affected. Trusted resources verification policies match source URIs against unanchored regex patterns, so an attacker who can influence the source URI and embed a trusted pattern as a substring can trigger an unintended policy match and change which verification keys apply. Upgrade to 1.0.2, 1.3.4, 1.6.2, 1.9.3, or 1.11.1 or later. As a workaround, anchor verification policy resource patterns with ^ and $ so they must match the full source string.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.5 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0026, the 18th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:13 UTC First seen by agentprime
  2. 31 Oct 2026, 14:13 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.