Cyber Resilience

CVE-2026-25542

Linuxfoundation Tekton Pipelines 0.43.0 – 1.11.0

Public PoC
Published
21 April 2026
Modified
22 May 2026
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
EPSS Score 0.0026 18th percentile
Risk Priority 49 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-25542 is a medium-severity Incorrect Regular Expression (CWE-185) vulnerability in Linuxfoundation Tekton Pipelines. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked at the 18th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Tekton Pipelines project provides k8s-style resources for declaring CI/CD-style pipelines. Starting in version 0.43.0 and prior to versions 1.0.2, 1.3.4, 1.6.2, 1.9.3, and 1.11.1, trusted resources verification policies match a resource source string (refSource.URI) against spec.resources[].pattern using regexp.MatchString. In Go,…

more

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. Versions 1.0.2, 1.3.4, 1.6.2, 1.9.3, and 1.11.1 fix the issue.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1566 Phishing Initial Access
Adversaries may send phishing messages to gain access to victim systems.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-40923Same product: Linuxfoundation Tekton Pipelines
CVE-2026-33211Same product: Linuxfoundation Tekton Pipelines
CVE-2026-40938Same product: Linuxfoundation Tekton Pipelines
CVE-2026-33022Same product: Linuxfoundation Tekton Pipelines
CVE-2023-37264Same product: Linuxfoundation Tekton Pipelines
CVE-2026-40161Same product: Linuxfoundation Tekton Pipelines
CVE-2026-40924Same product: Linuxfoundation Tekton Pipelines
CVE-2026-33418Shared CWE-185
CVE-2026-24398Shared CWE-185
CVE-2026-4296Shared CWE-185

Affected Assets

linuxfoundation
tekton pipelines
0.43.0 — 1.11.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover regex that fails to match or compare data as intended.

Requiring documented development standards and tools reduces the chance that incorrect regular expressions are written into validation or filtering logic.

An SDLC that incorporates security can embed reviews or tooling that catch malformed regular expressions before deployment.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require correct regex design, testing, and review to avoid improper matching.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development can detect regex-related flaws before release.

prevents

Secure development lifecycle includes validation of input-handling constructs such as regex.

prevents

Application security requirements can mandate correct regex design and testing.

prevents

Secure coding standards directly address proper construction and review of regular expressions.

References