# CVE-2026-76014: BusyBox FEATURE_WGET_TIMEOUT wget.c null pointer dereference

> A local attacker can cause a denial of service in BusyBox by triggering a null pointer dereference in the wget timeout handler.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-76014, GHSA-xwfg-2qxj-cwwg, OESA-2026-3683, OESA-2026-3684, OESA-2026-3685, OESA-2026-3686, OESA-2026-3763, UBUNTU-CVE-2026-76014

## What is CVE-2026-76014?

CVE-2026-76014 is a medium-severity vulnerability in BusyBox, published on 19 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability has been found in BusyBox up to 1.30.1. This vulnerability affects unknown code of the file networking/wget.c of the component FEATURE_WGET_TIMEOUT Handler. Such manipulation of the argument -T leads to null pointer dereference. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. The name of the patch is 83a40bf7a93c8ac093d33ab452222dd5b9eb57ff. A patch should be applied to remediate this issue.

Weakness: CWE-476 (NULL Pointer Dereference), CWE-404 (Improper Resource Shutdown or Release)

## Which versions are affected by CVE-2026-76014?


## How do I fix CVE-2026-76014?

Apply the vendor's patch.

## Is CVE-2026-76014 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-76014 and fix it if it is affected.

What it is: CVE-2026-76014 is a medium-severity vulnerability in BusyBox, published on 19 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-76014 exists.

Affected product: BusyBox. 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-2026-76014/ (Markdown: https://insights.sbomify.com/CVE-2026-76014/index.md)
```

## Sources

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

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