CLEANSTART-2026-QV01934: For HTTP/1 servers, when MaxBytesReader's limit is exceeded, "Connection: close" header is automatically set without synchronization, which might race with another header being set explicitly in th...

Published Nov 20, 2026
·
Updated

CVE-2026-97054 affects multiple packages. For HTTP/1 servers, when MaxBytesReader's limit is exceeded, "Connection: close" header is automatically set without synchronization, which might race with another header being set explicitly in the server handler. See references for individual vulnerability details.

Affected Software

36 affected componentsFixes available
cleanstart/argo-workflows<3.7.18-r3
3.7.18-r3
cleanstart/trino<483-r13
483-r13
cleanstart/prometheus-statsd-exporter<0.29.0-r6
0.29.0-r6
cleanstart/prometheus-statsd-exporter<0.31.0-r3
0.31.0-r3
cleanstart/access-log-exporter<0.3.20-r1
0.3.20-r1
cleanstart/prometheus-alertmanager<0.33.1-r7
0.33.1-r7
cleanstart/kyverno<1.15.3-r5
1.15.3-r5
cleanstart/kyverno<1.16.4-r10
1.16.4-r10
cleanstart/tempo<2.9.5-r3
2.9.5-r3
cleanstart/tempo<3.1.1-r3
3.1.1-r3
cleanstart/tempo<2.10.10-r2
2.10.10-r2
cleanstart/openbao<2.5.5-r2
2.5.5-r2
cleanstart/rundeck<6.3.0-r1
6.3.0-r1
cleanstart/kubernetes<1.36.6-r6
1.36.6-r6
cleanstart/kubernetes<1.35.10-r0
1.35.10-r0
cleanstart/kubernetes<1.35.7-r4
1.35.7-r4
cleanstart/kubernetes<1.37.2-r0
1.37.2-r0
cleanstart/trust-manager<0.24.0-r5
0.24.0-r5
cleanstart/trust-manager<0.21.1-r4
0.21.1-r4
cleanstart/opentelemetry-collector-contrib<0.163.0-r1
0.163.0-r1
cleanstart/prometheus-redis-exporter<1.93.0-r2
1.93.0-r2
cleanstart/prometheus-operator<0.92.1-r9
0.92.1-r9
cleanstart/external-dns<0.22.0-r6
0.22.0-r6
cleanstart/prometheus-operator<0.91.0-r13
0.91.0-r13
cleanstart/argo-cd<3.5.6-r3
3.5.6-r3
cleanstart/argo-cd<3.4.12-r1
3.4.12-r1
cleanstart/argo-cd<3.3.18-r1
3.3.18-r1
cleanstart/argo-cd<3.2.12-r12
3.2.12-r12
cleanstart/rclone<1.72.1-r16
1.72.1-r16
cleanstart/mailpit<1.32.0-r2
1.32.0-r2
cleanstart/argo-cd<3.3.19-r4
3.3.19-r4
cleanstart/haproxy-ingress<0.13.19-r8
0.13.19-r8
cleanstart/haproxy-ingress<0.14.12-r10
0.14.12-r10
cleanstart/vault<1.19.5-r9
1.19.5-r9
cleanstart/vault<1.20.4-r17
1.20.4-r17
cleanstart/nfs-subdir-external-provisioner<4.0.2-r7
4.0.2-r7

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-r3
  2. Upgrade

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

    Fixed in 483-r13
  3. Upgrade

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

    Fixed in 0.29.0-r6
  4. Upgrade

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

    Fixed in 0.31.0-r3
  5. Upgrade

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

    Fixed in 0.3.20-r1
  6. Upgrade

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

    Fixed in 0.33.1-r7
  7. Upgrade

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

    Fixed in 1.15.3-r5
  8. Upgrade

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

    Fixed in 1.16.4-r10
  9. Upgrade

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

    Fixed in 2.9.5-r3
  10. Upgrade

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

    Fixed in 3.1.1-r3
  11. Upgrade

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

    Fixed in 2.10.10-r2
  12. Upgrade

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

    Fixed in 2.5.5-r2
  13. Upgrade

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

    Fixed in 6.3.0-r1
  14. Upgrade

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

    Fixed in 1.36.6-r6
  15. Upgrade

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

    Fixed in 1.35.10-r0
  16. Upgrade

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

    Fixed in 1.35.7-r4
  17. Upgrade

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

    Fixed in 1.35.7-r5
  18. Upgrade

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

    Fixed in 1.37.2-r0
  19. Upgrade

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

    Fixed in 0.24.0-r5
  20. Upgrade

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

    Fixed in 0.21.1-r4
  21. Upgrade

    Upgrade cleanstart/opentelemetry-collector-contrib to a version that resolves this vulnerability.

    Fixed in 0.163.0-r1
  22. Upgrade

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

    Fixed in 1.93.0-r2
  23. Upgrade

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

    Fixed in 0.92.1-r9
  24. Upgrade

    Upgrade cleanstart/external-dns to a version that resolves this vulnerability.

    Fixed in 0.22.0-r6
  25. Upgrade

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

    Fixed in 0.91.0-r13
  26. Upgrade

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

    Fixed in 3.5.6-r3
  27. Upgrade

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

    Fixed in 3.4.12-r1
  28. Upgrade

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

    Fixed in 3.3.18-r1
  29. Upgrade

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

    Fixed in 3.2.12-r12
  30. Upgrade

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

    Fixed in 1.72.1-r16
  31. Upgrade

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

    Fixed in 1.32.0-r2
  32. Upgrade

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

    Fixed in 3.3.19-r4
  33. Upgrade

    Upgrade cleanstart/haproxy-ingress to a version that resolves this vulnerability.

    Fixed in 0.13.19-r8
  34. Upgrade

    Upgrade cleanstart/haproxy-ingress to a version that resolves this vulnerability.

    Fixed in 0.14.12-r10
  35. Upgrade

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

    Fixed in 1.19.5-r9
  36. Upgrade

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

    Fixed in 1.20.4-r17
  37. Upgrade

    Upgrade cleanstart/nfs-subdir-external-provisioner to a version that resolves this vulnerability.

    Fixed in 4.0.2-r7

Event History

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

Child vulnerabilities

Contains the following vulnerabilities.

Frequently Asked Questions

1

Which deployments should be prioritized for review?

Review deployments using cleanstart/argo-cd, cleanstart/kubernetes, cleanstart/tempo, cleanstart/prometheus-statsd-exporter, cleanstart/kyverno, cleanstart/trust-manager, cleanstart/prometheus-operator, or cleanstart/haproxy-ingress. The advisory states that the CVE affects multiple packages, but does not provide affected version ranges.

2

What conditions are required for exploitation?

The issue applies to HTTP/1 server handling when a MaxBytesReader limit is exceeded and the server handler explicitly sets another Connection header concurrently. The supplied vector indicates network access is possible without privileges or user interaction, while attack complexity is high.

3

What is the expected security impact?

The provided severity vector indicates high availability impact, with no stated confidentiality or integrity impact. The overall severity is medium, scored 5.9.

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