# CVE-2025-60876: Other in n/a

> BusyBox wget allows HTTP request splitting via control characters, enabling header injection and potential cache poisoning or security bypass.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Nov 2025
- **Updated:** 2 Jun 2026
- **Also known as:** AZL-69985, AZL-70043, BELL-CVE-2025-60876, DEBIAN-CVE-2025-60876, ECHO-76a8-cca4-145a, GHSA-48hw-cv6f-mcpj, MINI-3729-6w87-2929, OESA-2026-1879, OESA-2026-1880, OESA-2026-1881, OESA-2026-2700, OESA-2026-2701, OESA-2026-2702, RHSA-2026:7418, UBUNTU-CVE-2025-60876

## What is CVE-2025-60876?

CVE-2025-60876 is a medium-severity vulnerability in n/a, published on 10 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2025-60876?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `busybox` | Red Hat:hummingbird:1 | All versions | 0:1.37.0-7.1.hum1 |
| `busybox-petitboot` | Red Hat:hummingbird:1 | All versions | 0:1.37.0-7.1.hum1 |
| `busybox-shared` | Red Hat:hummingbird:1 | All versions | 0:1.37.0-7.1.hum1 |

Products: Busybox Busybox.

## How do I fix CVE-2025-60876?

Apply the vendor's patch.

## Is CVE-2025-60876 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-60876 exists.

Public exploit code:

- https://github.com/sirredbeard/CVE-2025-60876 (github_poc): https://github.com/sirredbeard/CVE-2025-60876

## Other vulnerabilities in n/a

- [CVE-2022-48174](https://insights.sbomify.com/CVE-2022-48174/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-42377](https://insights.sbomify.com/CVE-2021-42377/): Memory corruption in busybox (critical 9.8)
- [CVE-2016-2148](https://insights.sbomify.com/CVE-2016-2148/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-28391](https://insights.sbomify.com/CVE-2022-28391/): Command injection in n/a (high 8.8)
- [CVE-2017-16544](https://insights.sbomify.com/CVE-2017-16544/): Code injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-60876 and fix it if it is affected.

What it is: CVE-2025-60876 is a medium-severity vulnerability in n/a, published on 10 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-60876 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-60876/ (Markdown: https://insights.sbomify.com/CVE-2025-60876/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-60876
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-60876
- OSV: https://osv.dev/vulnerability/CVE-2025-60876

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-60876/
Summaries are generated and may contain mistakes; the official description above is the record.