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...

Published Nov 20, 2026
·
Updated

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

15 affected componentsFixes available
cleanstart/argo-workflows<3.7.18-r2
3.7.18-r2
cleanstart/access-log-exporter<0.3.20-r1
0.3.20-r1
cleanstart/kyverno<1.15.3-r5
1.15.3-r5
cleanstart/tempo<2.9.5-r3
2.9.5-r3
cleanstart/openbao<2.5.5-r2
2.5.5-r2
cleanstart/kubernetes<1.35.7-r5
1.35.7-r5
cleanstart/trust-manager<0.21.1-r4
0.21.1-r4
cleanstart/prometheus-operator<0.91.0-r8
0.91.0-r8
cleanstart/prometheus-node-exporter-fips<1.11.1-r9
1.11.1-r9
cleanstart/argo-cd<3.3.19-r3
3.3.19-r3
cleanstart/langfuse-worker<4.71.0-r1
4.71.0-r1
cleanstart/memcached-exporter<0.18.0-r2
0.18.0-r2
cleanstart/openbao<2.6.4-r2
2.6.4-r2
cleanstart/prometheus-node-exporter-fips<1.9.1-r3
1.9.1-r3
cleanstart/prometheus-node-exporter-fips<1.10.2-r8
1.10.2-r8

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade cleanstart/argo-workflows to a version that resolves this vulnerability.

    Fixed in 3.7.18-r2
  2. Upgrade

    Upgrade cleanstart/access-log-exporter to a version that resolves this vulnerability.

    Fixed in 0.3.20-r1
  3. Upgrade

    Upgrade cleanstart/kyverno to a version that resolves this vulnerability.

    Fixed in 1.15.3-r5
  4. Upgrade

    Upgrade cleanstart/kyverno to a version that resolves this vulnerability.

    Fixed in 1.15.3-r6
  5. Upgrade

    Upgrade cleanstart/tempo to a version that resolves this vulnerability.

    Fixed in 2.9.5-r3
  6. Upgrade

    Upgrade cleanstart/openbao to a version that resolves this vulnerability.

    Fixed in 2.5.5-r2
  7. Upgrade

    Upgrade cleanstart/kubernetes to a version that resolves this vulnerability.

    Fixed in 1.35.7-r5
  8. Upgrade

    Upgrade cleanstart/kubernetes to a version that resolves this vulnerability.

    Fixed in 1.35.7-r7
  9. Upgrade

    Upgrade cleanstart/kubernetes to a version that resolves this vulnerability.

    Fixed in 1.35.7-r4
  10. Upgrade

    Upgrade cleanstart/trust-manager to a version that resolves this vulnerability.

    Fixed in 0.21.1-r4
  11. Upgrade

    Upgrade cleanstart/prometheus-operator to a version that resolves this vulnerability.

    Fixed in 0.91.0-r8
  12. Upgrade

    Upgrade cleanstart/prometheus-node-exporter-fips to a version that resolves this vulnerability.

    Fixed in 1.11.1-r9
  13. Upgrade

    Upgrade cleanstart/argo-cd to a version that resolves this vulnerability.

    Fixed in 3.3.19-r3
  14. Upgrade

    Upgrade cleanstart/argo-cd to a version that resolves this vulnerability.

    Fixed in 3.3.19-r4
  15. Upgrade

    Upgrade cleanstart/langfuse-worker to a version that resolves this vulnerability.

    Fixed in 4.71.0-r1
  16. Upgrade

    Upgrade cleanstart/memcached-exporter to a version that resolves this vulnerability.

    Fixed in 0.18.0-r2
  17. Upgrade

    Upgrade cleanstart/openbao to a version that resolves this vulnerability.

    Fixed in 2.6.4-r2
  18. Upgrade

    Upgrade cleanstart/prometheus-node-exporter-fips to a version that resolves this vulnerability.

    Fixed in 1.9.1-r3
  19. Upgrade

    Upgrade cleanstart/prometheus-node-exporter-fips to a version that resolves this vulnerability.

    Fixed in 1.10.2-r8

Event History

Nov 20, 2026
Advisory Published
via OSV·12:46 AM
Data Sourced
via OSV·12:46 AM
DescriptionSeverityAffected Software

Child vulnerabilities

Contains the following vulnerabilities.

Frequently Asked Questions

1

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.

2

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.

3

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203