Vulnerabilities · 2025 · Busybox
CVE-2025-60876
Busybox vulnerability
BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20).
Affected products
Busybox. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Busybox runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- gist.github.com/subyumatest/41554af6a72aedaacaec026adc311092 · Exploit
- lists.busybox.net/pipermail/busybox/attachments/20250823/ccdc96ef/attachment-0001.htm
- lists.busybox.net/pipermail/busybox/attachments/20250828/e7f90492/attachment.htm
- cert-portal.siemens.com/productcert/html/ssa-253495.html
- nvd.nist.gov/vuln/detail/CVE-2025-60876
- cve.org/CVERecord?id=CVE-2025-60876
More vulnerabilities in Busybox products
CVE-2025-46394CVE-2023-42366CVE-2023-42365CVE-2023-42364CVE-2023-42363CVE-2023-39810CVE-2022-48174CVE-2022-30065All 41
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.