CVE-2026-40924

Tekton Pipelines: HTTP Resolver Unbounded Response Body Read Enables Denial of Service via Memory Exhaustion

MEDIUM
6.5
CVSS Score
Published: April 21, 2026 at 08:47 PM UTC
Updated: October 26, 2026 at 10:10 PM UTC
2 products affected across 2 vendorsTekton PipelinesPipeline

Using pipeline by tektoncd?

Get instant alerts when new vulnerabilities affect pipeline - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.5
Exploit prediction
EPSS 0.3%
SSVC
PoC

Description

Tekton Pipelines project provides k8s-style resources for declaring CI/CD-style pipelines. Prior to 1.11.1, the HTTP resolver's FetchHttpResource function calls io.ReadAll(resp.Body) with no response body size limit. Any tenant with permission to create TaskRuns or PipelineRuns that reference the HTTP resolver can point it at an attacker-controlled HTTP server that returns a very large response body within the 1-minute timeout window, causing the tekton-pipelines-resolvers pod to be OOM-killed by Kubernetes. Because all resolver types (Git, Hub, Bundle, Cluster, HTTP) run in the same pod, crashing this pod denies resolution service to the entire cluster. Repeated exploitation causes a sustained crash loop. The same vulnerable code path is reached by both the deprecated pkg/resolution/resolver/http and the current pkg/remoteresolution/resolver/http implementations. This vulnerability is fixed in 1.11.1.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

1.0.0 ≤ v < 1.0.21.10.0 ≤ v < 1.11.11.2.0 ≤ v < 1.3.41.4.0 ≤ v < 1.6.21.7.0 ≤ v < 1.9.3
Affected range stops below 1.0.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.11.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.3.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.6.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.9.3, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (2)

x_refsource_CONFIRMExploitVendor Advisory
Source: cverecord
https://github.com/tektoncd/pipeline/security/advisories/GHSA-m2cx-gpqf-qf74
x_refsource_MISCRelease Notes
Source: cverecord
https://github.com/tektoncd/pipeline/releases/tag/v1.11.1

SSVC — Action Prioritization

SSVCPoCNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6.5MEDIUMGitHub_M
Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-400

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card