Knowledge · Vulnerabilities by version

BusyBox 1.26.2: 65 known CVEs

65 CVEs, 3 of them critical and 0 actively exploited.

As of 13 Nov 2026, 65 CVEs are known for BusyBox 1.26.2, 3 critical and 26 high. 1.38.0, the newest listed version, still carries 38 of them.

Data queried 13 November 2026 · Page updated 13 November 2026 · 4 min read

At a glance
Version
BusyBox 1.26.2
Known CVEs
65
Critical / high
3 / 26
Actively exploited (CISA KEV)
0
Confirmed by the vendor
0

Checked on 13 Nov 2026

Which CVEs affect BusyBox 1.26.2?

CVESeverityCVSSFixed fromNote
CVE-2018-1000517critical9.81.29.0per vulnerability databases
CVE-2021-42377critical9.8not statedper vulnerability databases
CVE-2022-48174critical9.8not statedper vulnerability databases
CVE-2017-16544high8.8not statedper vulnerability databases
CVE-2022-28391high8.8not statedper vulnerability databases
CVE-2018-1000500high8.11.32.0per vulnerability databases
CVE-2022-30065high7.8not statedper vulnerability databases
CVE-2023-39810high7.8not statedper vulnerability databases
CVE-2026-90954high7.8not statedper vulnerability databases
CVE-2026-124741high7.6not statedper vulnerability databases
CVE-2018-20679high7.51.30.0per vulnerability databases
CVE-2019-5747high7.5not statedper vulnerability databases
CVE-2026-124737high7.5not statedper vulnerability databases
CVE-2026-124739high7.5not statedper vulnerability databases
CVE-2026-124747high7.5not statedper vulnerability databases
CVE-2026-88830high7.5not statedper vulnerability databases
CVE-2026-88832high7.3not statedper vulnerability databases
CVE-2021-42378high7.2not statedper vulnerability databases
CVE-2021-42379high7.2not statedper vulnerability databases
CVE-2021-42381high7.2not statedper vulnerability databases
CVE-2021-42382high7.2not statedper vulnerability databases
CVE-2021-42383high7.2not statedper vulnerability databases
CVE-2021-42384high7.2not statedper vulnerability databases
CVE-2021-42385high7.2not statedper vulnerability databases
CVE-2021-42386high7.2not statedper vulnerability databases
CVE-2026-29004high7.2not statedper vulnerability databases
CVE-2026-88829high7.2not statedper vulnerability databases
CVE-2026-26157high7.0not statedper vulnerability databases
CVE-2026-26158high7.0not statedper vulnerability databases
CVE-2026-88839medium6.7not statedper vulnerability databases
CVE-2025-60876medium6.5not statedper vulnerability databases
CVE-2026-88833medium6.5not statedper vulnerability databases
CVE-2026-88837medium6.5not statedper vulnerability databases
CVE-2026-108119medium6.3not statedper vulnerability databases
CVE-2026-124744medium6.3not statedper vulnerability databases
CVE-2026-124745medium6.3not statedper vulnerability databases
CVE-2026-88835medium6.1not statedper vulnerability databases
CVE-2026-92205medium6.1not statedper vulnerability databases
CVE-2015-9261medium5.51.27.2per vulnerability databases
CVE-2017-15873medium5.5not statedper vulnerability databases
CVE-2017-15874medium5.5not statedper vulnerability databases
CVE-2021-42373medium5.5not statedper vulnerability databases
CVE-2021-42375medium5.5not statedper vulnerability databases
CVE-2021-42376medium5.51.34.0per vulnerability databases
CVE-2023-42363medium5.5not statedper vulnerability databases
CVE-2023-42364medium5.5not statedper vulnerability databases
CVE-2023-42365medium5.5not statedper vulnerability databases
CVE-2023-42366medium5.5not statedper vulnerability databases
CVE-2026-124742medium5.5not statedper vulnerability databases
CVE-2026-124743medium5.5not statedper vulnerability databases
CVE-2026-124746medium5.5not statedper vulnerability databases
CVE-2026-88838medium5.5not statedper vulnerability databases
CVE-2026-124738medium5.3not statedper vulnerability databases
CVE-2026-88831medium5.3not statedper vulnerability databases
CVE-2026-88840medium5.3not statedper vulnerability databases
CVE-2026-38754medium5.1not statedper vulnerability databases
CVE-2026-38753medium4.9not statedper vulnerability databases
CVE-2026-88834low3.7not statedper vulnerability databases
CVE-2025-46394low3.3not statedper vulnerability databases
CVE-2026-88842low3.3not statedper vulnerability databases
CVE-2026-38752low2.9not statedper vulnerability databases
CVE-2026-38755low2.9not statedper vulnerability databases
CVE-2024-58251low2.5not statedper vulnerability databases
CVE-2026-76014low1.9not statedper vulnerability databases
CVE-2026-88841not ratednot ratednot statedper vulnerability databases

Which BusyBox version do I need to upgrade to?

Fixed in BusyBox 1.27.2: 1 CVE of this version.

Fixed in BusyBox 1.29.0: 1 CVE of this version.

Fixed in BusyBox 1.30.0: 1 CVE of this version.

Fixed in BusyBox 1.32.0: 1 CVE of this version.

Fixed in BusyBox 1.34.0: 1 CVE of this version.

No fix version stated: 60.

What changed against BusyBox 1.26.1?

No CVE of 1.26.1 dropped out in 1.26.2.

No CVE was added in 1.26.2.

What does the number mean for a device?

Counted are the CVEs public sources name for BusyBox version 1.26.2 (NVD, OSV, Vendor advisories). "Confirmed by the vendor" means the CVE record or advisory comes from the vendor itself and names this version as affected. Third-party records are counted but not marked as confirmed.

Whether a CVE is exploitable in a given device depends on which functions of the library the build contains and how they are configured. The list shows what is known for the version.

Licence notes of the sources: OSV: CC BY 4.0.

Questions

How many CVEs does BusyBox 1.26.2 have?

As of 13 Nov 2026, 65 CVEs are known for BusyBox 1.26.2, 3 critical and 26 high. 1.38.0, the newest listed version, still carries 38 of them.

From which version are the CVEs of BusyBox 1.26.2 fixed?

No newer listed version is free of all 65 CVEs. The "Fixed from" column names the fix version per CVE for this release line where a source states one.

Sources

  1. [1]NVD
  2. [2]OSV

Which BusyBox version is in your build?

Vendor SDKs ship their own versions. Upload the AXF, HEX or firmware image: we read the versions from the binary and match the CVEs. Report and SBOM within three working days, free. The reports are in German.