CLEANSTART-2026-GV15775: Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing
CVE-2026-78660 affects multiple packages. Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. 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-r5 - 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/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 access does an attacker need to exploit this issue?
The supplied vector indicates the issue is remotely reachable over the network and requires neither prior privileges nor user interaction. Attack complexity is rated low.
Which deployments should be prioritized for review?
Review deployments of cleanstart/prometheus-node-exporter-fips, cleanstart/openbao, cleanstart/argo-workflows, cleanstart/access-log-exporter, cleanstart/kyverno, cleanstart/tempo, cleanstart/kubernetes, and cleanstart/trust-manager that expose HTTP/2-capable network services.
What is the stated security impact?
The provided severity vector rates the issue high at 7.5 and identifies high integrity impact. It identifies no confidentiality or availability impact.