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...
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
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-r3 - Upgrade
Upgrade
cleanstart/trinoto a version that resolves this vulnerability.Fixed in 483-r13 - Upgrade
Upgrade
cleanstart/prometheus-statsd-exporterto a version that resolves this vulnerability.Fixed in 0.29.0-r6 - Upgrade
Upgrade
cleanstart/prometheus-statsd-exporterto a version that resolves this vulnerability.Fixed in 0.31.0-r3 - Upgrade
Upgrade
cleanstart/access-log-exporterto a version that resolves this vulnerability.Fixed in 0.3.20-r1 - Upgrade
Upgrade
cleanstart/prometheus-alertmanagerto a version that resolves this vulnerability.Fixed in 0.33.1-r7 - 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.16.4-r10 - Upgrade
Upgrade
cleanstart/tempoto a version that resolves this vulnerability.Fixed in 2.9.5-r3 - Upgrade
Upgrade
cleanstart/tempoto a version that resolves this vulnerability.Fixed in 3.1.1-r3 - Upgrade
Upgrade
cleanstart/tempoto a version that resolves this vulnerability.Fixed in 2.10.10-r2 - Upgrade
Upgrade
cleanstart/openbaoto a version that resolves this vulnerability.Fixed in 2.5.5-r2 - Upgrade
Upgrade
cleanstart/rundeckto a version that resolves this vulnerability.Fixed in 6.3.0-r1 - Upgrade
Upgrade
cleanstart/kubernetesto a version that resolves this vulnerability.Fixed in 1.36.6-r6 - Upgrade
Upgrade
cleanstart/kubernetesto a version that resolves this vulnerability.Fixed in 1.35.10-r0 - 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/kubernetesto a version that resolves this vulnerability.Fixed in 1.37.2-r0 - Upgrade
Upgrade
cleanstart/trust-managerto a version that resolves this vulnerability.Fixed in 0.24.0-r5 - Upgrade
Upgrade
cleanstart/trust-managerto a version that resolves this vulnerability.Fixed in 0.21.1-r4 - Upgrade
Upgrade
cleanstart/opentelemetry-collector-contribto a version that resolves this vulnerability.Fixed in 0.163.0-r1 - Upgrade
Upgrade
cleanstart/prometheus-redis-exporterto a version that resolves this vulnerability.Fixed in 1.93.0-r2 - Upgrade
Upgrade
cleanstart/prometheus-operatorto a version that resolves this vulnerability.Fixed in 0.92.1-r9 - Upgrade
Upgrade
cleanstart/external-dnsto a version that resolves this vulnerability.Fixed in 0.22.0-r6 - Upgrade
Upgrade
cleanstart/prometheus-operatorto a version that resolves this vulnerability.Fixed in 0.91.0-r13 - Upgrade
Upgrade
cleanstart/argo-cdto a version that resolves this vulnerability.Fixed in 3.5.6-r3 - Upgrade
Upgrade
cleanstart/argo-cdto a version that resolves this vulnerability.Fixed in 3.4.12-r1 - Upgrade
Upgrade
cleanstart/argo-cdto a version that resolves this vulnerability.Fixed in 3.3.18-r1 - Upgrade
Upgrade
cleanstart/argo-cdto a version that resolves this vulnerability.Fixed in 3.2.12-r12 - Upgrade
Upgrade
cleanstart/rcloneto a version that resolves this vulnerability.Fixed in 1.72.1-r16 - Upgrade
Upgrade
cleanstart/mailpitto a version that resolves this vulnerability.Fixed in 1.32.0-r2 - Upgrade
Upgrade
cleanstart/argo-cdto a version that resolves this vulnerability.Fixed in 3.3.19-r4 - Upgrade
Upgrade
cleanstart/haproxy-ingressto a version that resolves this vulnerability.Fixed in 0.13.19-r8 - Upgrade
Upgrade
cleanstart/haproxy-ingressto a version that resolves this vulnerability.Fixed in 0.14.12-r10 - Upgrade
Upgrade
cleanstart/vaultto a version that resolves this vulnerability.Fixed in 1.19.5-r9 - Upgrade
Upgrade
cleanstart/vaultto a version that resolves this vulnerability.Fixed in 1.20.4-r17 - Upgrade
Upgrade
cleanstart/nfs-subdir-external-provisionerto a version that resolves this vulnerability.Fixed in 4.0.2-r7
Event History
Frequently Asked Questions
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.
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.
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.