CLEANSTART-2026-KP67846: malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGS_INITIAL_WINDOW...
CVE-2026-78669 affects multiple packages. A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGSINITIALWINDOWSIZE values. 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
Which deployments are exposed to this denial-of-service condition?
Deployments of the listed affected packages are exposed when they act as an HTTP/2 client or server and can communicate with a malicious HTTP/2 peer. The affected software listed is cleanstart/prometheus-node-exporter-fips, cleanstart/openbao, cleanstart/argo-workflows, cleanstart/access-log-exporter, cleanstart/kyverno, cleanstart/tempo, cleanstart/kubernetes, and cleanstart/trust-manager.
What does an attacker need to exploit it?
The attacker needs network access to communicate as an HTTP/2 peer; no privileges or user interaction are required. They exploit the condition by opening many streams and sending many small SETTINGS frames containing SETTINGS_INITIAL_WINDOW_SIZE values.
What is the expected impact?
Successful exploitation can cause excessive CPU consumption in either the HTTP/2 client or server. The reported impact is availability loss; no confidentiality or integrity impact is indicated.