A heap overflow in the ifsbreakup() function (shell/ash.c) of Busybox v1.38.0 allows attackers to cause a Denial of Service (DoS) via supplying a crafted input.
CVE-2026-38754
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-16. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 34%
- KEV
- Not listed
Published
July 15, 2026
Last Modified
July 22, 2026
Advisory Details (2)
Auto-updated Jul 16, 2026[PATCH] ash: fix out-of-bounds read in ifsbreakup()
https://lists.busybox.net/pipermail/busybox/2026-June/092353.htmlVendor Advisories for CVE-2026-38754(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- CVE-2026-38754Microsoft Security Response Center (MSRC)High
A heap overflow in the ifsbreakup() function (shell/ash.c) of Busybox v1.38.0 allows attackers to cause a Denial of Service (DoS) via supplying a crafted input.
- GHSA-jj7c-h3wm-vjfwGitHub Security AdvisoriesHigh
A heap overflow in the ifsbreakup() function (shell/ash.c) of Busybox v1.38.0 allows attackers to...
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | busybox-main-1.37.0-8.1.hum1 | 2026-07-16 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| busybox | 1:1.30.1-6 ... 1:1.38.0-3 (35 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| busybox | 1:1.35.0-4 ... 1:1.38.0-3 (28 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| busybox | 1:1.37.0-10 ... 1:1.38.0-3 (9 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| busybox | 1:1.37.0-10 ... 1:1.38.0-2 (8 versions) | 1:1.38.0-3 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(1)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 29× in last 7d / 152× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 207 total refreshes for this CVE.
- 2026-08-30 03:59 UTCEG score recompute
- 2026-08-30 03:59 UTCVendor advisory
- 2026-08-30 03:59 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-28 02:27 UTCEG score recompute
- 2026-08-28 02:27 UTCVendor advisory
- 2026-08-28 02:27 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 13:46 UTCGHSA enrichment
- 2026-08-27 01:13 UTCEG score recompute
- 2026-08-27 01:13 UTCVendor advisory
- 2026-08-27 01:13 UTCGHSA enrichment
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 12:46 UTCVendor advisory
- 2026-08-26 12:45 UTCGHSA enrichment
- 2026-08-25 23:58 UTCEG score recompute
- 2026-08-25 23:58 UTCVendor advisory
- 2026-08-25 23:58 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 08:51 UTCVendor advisory
- 2026-08-25 08:51 UTCGHSA enrichment
- 2026-08-24 19:35 UTCEG score recompute
- 2026-08-24 19:35 UTCVendor advisory
- 2026-08-24 19:35 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-08-24 06:25 UTCVendor advisory
- 2026-08-24 06:25 UTCGHSA enrichment
- 2026-08-23 17:39 UTCVendor advisory
- 2026-08-23 17:39 UTCGHSA enrichment
- 2026-08-23 05:12 UTCVendor advisory
- 2026-08-23 05:12 UTCGHSA enrichment
- 2026-08-22 16:44 UTCVendor advisory
- 2026-08-22 16:44 UTCGHSA enrichment
- 2026-08-22 04:15 UTCEG score recompute
- 2026-08-22 04:15 UTCVendor advisory
- 2026-08-22 04:15 UTCGHSA enrichment
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 15:41 UTCGHSA enrichment
- 2026-08-21 03:08 UTCEG score recompute
- 2026-08-21 03:08 UTCVendor advisory
- 2026-08-21 03:08 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 14:38 UTCVendor advisory
- 2026-08-20 14:38 UTCGHSA enrichment
- 2026-08-20 00:21 UTCEG score recompute
- 2026-08-20 00:21 UTCVendor advisory
- 2026-08-20 00:21 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-19 11:23 UTCVendor advisory
- 2026-08-19 11:23 UTCGHSA enrichment
- 2026-08-18 22:52 UTCEG score recompute
- 2026-08-18 22:52 UTCVendor advisory
- 2026-08-18 22:51 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 10:20 UTCVendor advisory
- 2026-08-18 10:20 UTCGHSA enrichment
- 2026-08-17 21:52 UTCEG score recompute
- 2026-08-17 21:52 UTCVendor advisory
- 2026-08-17 21:52 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 09:13 UTCVendor advisory
- 2026-08-17 09:13 UTCGHSA enrichment
- 2026-08-16 20:46 UTCEG score recompute
- 2026-08-16 20:46 UTCVendor advisory
- 2026-08-16 20:46 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 08:19 UTCEG score recompute
- 2026-08-16 08:19 UTCVendor advisory
- 2026-08-16 08:19 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 19:52 UTCVendor advisory
- 2026-08-15 19:52 UTCGHSA enrichment
- 2026-08-15 07:25 UTCEG score recompute
- 2026-08-15 07:25 UTCVendor advisory
- 2026-08-15 07:25 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 18:10 UTCVendor advisory
- 2026-08-14 18:10 UTCGHSA enrichment
- 2026-08-14 05:42 UTCEG score recompute
- 2026-08-14 05:42 UTCVendor advisory
- 2026-08-14 05:42 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 17:15 UTCVendor advisory
- 2026-08-13 17:15 UTCGHSA enrichment
- 2026-08-13 04:48 UTCGHSA enrichment
- 2026-08-12 16:21 UTCEG score recompute
- 2026-08-12 16:21 UTCVendor advisory
- 2026-08-12 16:21 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 03:54 UTCVendor advisory
- 2026-08-12 03:54 UTCGHSA enrichment
- 2026-08-11 15:27 UTCEG score recompute
- 2026-08-11 15:27 UTCVendor advisory
- 2026-08-11 15:27 UTCGHSA enrichment
- 2026-08-11 13:43 UTCEPSS rescore
- 2026-08-11 03:00 UTCEG score recompute
- 2026-08-11 03:00 UTCVendor advisory
- 2026-08-11 03:00 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 14:33 UTCGHSA enrichment
Frequently asked(5)
What is CVE-2026-38754?
When was CVE-2026-38754 disclosed?
Is CVE-2026-38754 actively exploited?
What is the CVSS score of CVE-2026-38754?
How do I remediate CVE-2026-38754?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-38754
Is Your Infrastructure Affected by CVE-2026-38754?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.