CLEANSTART-2026-BD63129: When an HTTP server handler sends a 2xx response to an HTTP/1 CONNECT request and returns without hijacking the connection, the server improperly continues to read and serve requests from the conne...
CVE-2026-94439 affects multiple packages. When an HTTP server handler sends a 2xx response to an HTTP/1 CONNECT request and returns without hijacking the connection, the server improperly continues to read and serve requests from the connection. 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/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-r4 - Upgrade
Upgrade
cleanstart/kubernetesto a version that resolves this vulnerability.Fixed in 1.35.7-r5 - 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/langfuse-workerto a version that resolves this vulnerability.Fixed in 4.71.0-r1 - 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 should be reviewed for exposure?
Review deployments of cleanstart/prometheus-node-exporter-fips, cleanstart/argo-workflows, cleanstart/access-log-exporter, cleanstart/kyverno, cleanstart/openbao, cleanstart/kubernetes, cleanstart/trust-manager, and cleanstart/prometheus-operator.
What level of attacker access is required?
The supplied severity vector indicates network-based exploitation with low attack complexity. It requires no privileges and no user interaction.
What is the expected security impact?
The severity vector rates confidentiality impact as high. It indicates no integrity or availability impact.