CLEANSTART-2026-IL93282: When parsing a Range header containing a large number of small ranges, FileServer(FS), ServeContent, and ServeFile(FS) can consume an excessive amount of CPU
CVE-2026-78667 affects multiple packages. When parsing a Range header containing a large number of small ranges, FileServer(FS), ServeContent, and ServeFile(FS) can consume an excessive amount of CPU. 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
What access does an attacker need to trigger this issue?
The supplied vector indicates network access is sufficient; no privileges or user interaction are required. Exploitation involves sending an HTTP Range header with a large number of small ranges.
What is the likely operational impact?
Successful exploitation can cause excessive CPU consumption, resulting in an availability impact. The supplied severity vector indicates no confidentiality or integrity impact.
Which deployed components should be reviewed?
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. The provided data does not identify affected versions or configurations.