CLEANSTART-2026-WR64207: HTTP/2 server can refund connection-level flow control twice for the same data: Once when a client resets a stream (refunding data for any sent-but-unread portion of the stream), and again when a r...
CVE-2026-78663 affects multiple packages. The HTTP/2 server can refund connection-level flow control twice for the same data: Once when a client resets a stream (refunding data for any sent-but-unread portion of the stream), and again when a request handler reads the buffered data. See references for individual vulnerability details.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
cleanstart/argo-workflowsto a version that resolves this vulnerability.Fixed in 3.7.18-r2 - Upgrade
Upgrade
cleanstart/access-log-exporterto a version that resolves this vulnerability.Fixed in 0.3.20-r1 - Upgrade
Upgrade
cleanstart/kyvernoto a version that resolves this vulnerability.Fixed in 1.15.3-r5 - Upgrade
Upgrade
cleanstart/kyvernoto a version that resolves this vulnerability.Fixed in 1.15.3-r6 - Upgrade
Upgrade
cleanstart/tempoto a version that resolves this vulnerability.Fixed in 2.9.5-r3 - Upgrade
Upgrade
cleanstart/openbaoto a version that resolves this vulnerability.Fixed in 2.5.5-r2 - Upgrade
Upgrade
cleanstart/kubernetesto a version that resolves this vulnerability.Fixed in 1.35.7-r7 - Upgrade
Upgrade
cleanstart/kubernetesto a version that resolves this vulnerability.Fixed in 1.35.7-r4 - Upgrade
Upgrade
cleanstart/kubernetesto a version that resolves this vulnerability.Fixed in 1.35.7-r5 - Upgrade
Upgrade
cleanstart/trust-managerto a version that resolves this vulnerability.Fixed in 0.21.1-r4 - Upgrade
Upgrade
cleanstart/prometheus-operatorto a version that resolves this vulnerability.Fixed in 0.91.0-r8 - Upgrade
Upgrade
cleanstart/prometheus-node-exporter-fipsto a version that resolves this vulnerability.Fixed in 1.11.1-r9 - Upgrade
Upgrade
cleanstart/argo-cdto a version that resolves this vulnerability.Fixed in 3.3.19-r3 - Upgrade
Upgrade
cleanstart/argo-cdto a version that resolves this vulnerability.Fixed in 3.3.19-r4 - Upgrade
Upgrade
cleanstart/langfuse-workerto a version that resolves this vulnerability.Fixed in 4.71.0-r1 - Upgrade
Upgrade
cleanstart/memcached-exporterto a version that resolves this vulnerability.Fixed in 0.18.0-r2 - Upgrade
Upgrade
cleanstart/openbaoto a version that resolves this vulnerability.Fixed in 2.6.4-r2 - Upgrade
Upgrade
cleanstart/prometheus-node-exporter-fipsto a version that resolves this vulnerability.Fixed in 1.9.1-r3 - Upgrade
Upgrade
cleanstart/prometheus-node-exporter-fipsto a version that resolves this vulnerability.Fixed in 1.10.2-r8
Event History
Frequently Asked Questions
What does an attacker need to exploit this issue?
The vulnerability is remotely exploitable over the network and requires no privileges or user interaction. Exploitation involves resetting an HTTP/2 stream while request data is buffered and later read by the request handler.
What is the likely operational impact?
The double refund can incorrectly increase available connection-level HTTP/2 flow-control credit. The reported impact is high integrity and availability impact, with no reported confidentiality impact.
Which deployments should be prioritized for investigation?
Prioritize deployments using cleanstart/prometheus-node-exporter-fips, cleanstart/openbao, cleanstart/argo-workflows, cleanstart/access-log-exporter, cleanstart/kyverno, cleanstart/tempo, cleanstart/kubernetes, or cleanstart/trust-manager where they operate an HTTP/2 server accessible to untrusted clients.