BusyBox wget up to 1.3.7 HTTP Request injection

Summaryinfo

A vulnerability, which was classified as problematic, has been found in BusyBox wget up to 1.3.7. This affects an unknown part of the component HTTP Request Handler. Performing a manipulation results in injection. This vulnerability was named CVE-2025-60876. There is no available exploit.

Detailsinfo

A vulnerability was found in BusyBox wget up to 1.3.7. It has been classified as problematic. This affects an unknown functionality of the component HTTP Request Handler. The manipulation with an unknown input leads to a injection vulnerability. CWE is classifying the issue as CWE-74. The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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).

The advisory is shared at lists.busybox.net. This vulnerability is uniquely identified as CVE-2025-60876 since 09/26/2025. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/02/2026). MITRE ATT&CK project uses the attack technique T1055 for this issue.

The vulnerability scanner Nessus provides a plugin with the ID 274730 (Linux Distros Unpatched Vulnerability : CVE-2025-60876), which helps to determine the existence of the flaw in a target environment.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at Tenable (274730). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Automation Software

Vendor

• BusyBox

Name

• wget

Version

• 1.3.0
• 1.3.1
• 1.3.2
• 1.3.3
• 1.3.4
• 1.3.5
• 1.3.6
• 1.3.7

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion