Bug 2460365 (CVE-2026-40924)

Summary:	CVE-2026-40924 github.com/tektoncd/pipeline: Tekton Pipelines: Denial of Service via large HTTP response body
Product:	[Other] Security Response	Reporter:	OSIDB Bzimport <bzimport>
Component:	vulnerability	Assignee:	Product Security <prodsec-ir-bot>
Status:	NEW ---	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	anpicker, bparees, dfreiber, dhanak, drosa, drow, dsimansk, eborisov, fdeutsch, hasun, jburrell, jfula, jkoehler, jowilson, kingland, kverlaen, lball, lphiri, mnovotny, ngough, nyancey, ometelka, oramraz, ptisnovs, sausingh, smullick, stirabos, syedriko, thason, veshanka, vkumar, xdharmai
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:	A flaw was found in Tekton Pipelines. A local user with specific permissions to create TaskRuns or PipelineRuns can exploit this by directing the HTTP resolver to an attacker-controlled server. This server can return a very large response body, leading to the tekton-pipelines-resolvers pod consuming excessive memory and being terminated by Kubernetes. Repeated exploitation of this resource exhaustion vulnerability can cause a sustained denial of service for the entire cluster's resolution services.	Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-04-21 21:06:42 UTC

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.

Comment 5 Vipul Nair 2026-04-29 08:30:02 UTC

purely a denial of service flaw,doesnt require tracker.s