CVE-2025-60876: Critical severity Busybox wget 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 Software
Event History
Frequently Asked Questions
What is the vulnerability CVE-2025-60876?
CVE-2025-60876 is a vulnerability in BusyBox wget versions up to 1.3.7 that allows crafted HTTP requests to inject attacker-controlled headers through improper handling of newline characters.
What is the severity of CVE-2025-60876?
CVE-2025-60876 is considered a critical vulnerability due to its potential for HTTP request header injection.
How do I fix CVE-2025-60876?
To mitigate CVE-2025-60876, update BusyBox wget to a version that is newer than 1.3.7.
Which versions of BusyBox wget are affected by CVE-2025-60876?
CVE-2025-60876 affects BusyBox wget versions up to and including 1.3.7.
Can CVE-2025-60876 lead to remote code execution?
CVE-2025-60876 does not directly lead to remote code execution, but it can facilitate further attacks by allowing header injection.