CVE-2026-38755

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

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.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

A heap overflow in the evalcommand() function (shell/ash.c) of Busybox v1.38.0 allows attackers to cause a Denial of Service (DoS) via supplying a crafted input.

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 computed
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

July 15, 2026

Last Modified

July 20, 2026

Advisory Details (2)

Auto-updated Jul 16, 2026
No patch confirmed yet.
generic

[PATCH] ash: fix stack overflow in evalfun()

https://lists.busybox.net/pipermail/busybox/2026-June/092354.html
generic
https://busybox.com

Vendor Advisories for CVE-2026-38755(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatbusybox-main-1.37.0-8.2.hum12026-07-20redhat

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)
PackageVulnerable rangeFixed inDependents
busybox1:1.30.1-6 ... 1:1.38.0-3 (35 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
busybox1:1.35.0-4 ... 1:1.38.0-3 (28 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
busybox1:1.37.0-10 ... 1:1.38.0-3 (9 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
busybox1: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.

Data Freshness Timeline

(refreshed 16× in last 7d / 92× 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 258 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 04:48 UTCEG score recompute
  4. 2026-09-18 04:48 UTCVendor advisory
  5. 2026-09-18 04:48 UTCGHSA enrichment
  6. 2026-09-17 19:30 UTCEPSS rescore
  7. 2026-09-16 14:08 UTCEPSS rescore
  8. 2026-09-16 05:15 UTCEPSS rescore
  9. 2026-09-15 03:11 UTCEPSS rescore
  10. 2026-09-13 23:14 UTCEG score recompute
  11. 2026-09-13 23:14 UTCVendor advisory
  12. 2026-09-13 23:14 UTCGHSA enrichment
  13. 2026-09-13 16:47 UTCEPSS rescore
  14. 2026-09-13 07:27 UTCEG score recompute
  15. 2026-09-13 07:27 UTCVendor advisory
  16. 2026-09-13 07:27 UTCGHSA enrichment
  17. 2026-09-12 15:01 UTCEPSS rescore
  18. 2026-09-12 13:06 UTCVendor advisory
  19. 2026-09-12 13:06 UTCGHSA enrichment
  20. 2026-09-11 21:50 UTCEG score recompute
  21. 2026-09-11 21:50 UTCVendor advisory
  22. 2026-09-11 21:50 UTCGHSA enrichment
  23. 2026-09-11 14:53 UTCEPSS rescore
  24. 2026-09-11 09:37 UTCEPSS rescore
  25. 2026-09-10 09:34 UTCEPSS rescore
Show 75 more
  1. 2026-09-08 22:00 UTCEPSS rescore
  2. 2026-09-08 00:59 UTCEG score recompute
  3. 2026-09-08 00:59 UTCVendor advisory
  4. 2026-09-08 00:59 UTCGHSA enrichment
  5. 2026-09-07 16:01 UTCEPSS rescore
  6. 2026-09-06 13:47 UTCEPSS rescore
  7. 2026-09-06 13:30 UTCVendor advisory
  8. 2026-09-06 13:30 UTCGHSA enrichment
  9. 2026-09-05 20:54 UTCEG score recompute
  10. 2026-09-05 20:54 UTCVendor advisory
  11. 2026-09-05 20:54 UTCGHSA enrichment
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-02 14:12 UTCEPSS rescore
  14. 2026-09-01 13:53 UTCEPSS rescore
  15. 2026-09-01 04:39 UTCEPSS rescore
  16. 2026-08-31 05:15 UTCEG score recompute
  17. 2026-08-31 05:15 UTCVendor advisory
  18. 2026-08-31 05:15 UTCGHSA enrichment
  19. 2026-08-30 19:17 UTCEPSS rescore
  20. 2026-08-30 16:32 UTCVendor advisory
  21. 2026-08-30 16:32 UTCGHSA enrichment
  22. 2026-08-30 03:59 UTCEG score recompute
  23. 2026-08-30 03:59 UTCVendor advisory
  24. 2026-08-30 03:59 UTCGHSA enrichment
  25. 2026-08-30 01:22 UTCEPSS rescore
  26. 2026-08-28 21:41 UTCEPSS rescore
  27. 2026-08-28 02:27 UTCEG score recompute
  28. 2026-08-28 02:27 UTCVendor advisory
  29. 2026-08-28 02:27 UTCGHSA enrichment
  30. 2026-08-27 14:25 UTCEPSS rescore
  31. 2026-08-27 13:52 UTCVendor advisory
  32. 2026-08-27 13:52 UTCGHSA enrichment
  33. 2026-08-27 01:19 UTCEG score recompute
  34. 2026-08-27 01:19 UTCVendor advisory
  35. 2026-08-27 01:19 UTCGHSA enrichment
  36. 2026-08-26 14:46 UTCEPSS rescore
  37. 2026-08-26 12:46 UTCVendor advisory
  38. 2026-08-26 12:45 UTCGHSA enrichment
  39. 2026-08-25 23:58 UTCEG score recompute
  40. 2026-08-25 23:58 UTCVendor advisory
  41. 2026-08-25 23:58 UTCGHSA enrichment
  42. 2026-08-25 13:49 UTCEPSS rescore
  43. 2026-08-25 08:51 UTCVendor advisory
  44. 2026-08-25 08:51 UTCGHSA enrichment
  45. 2026-08-24 19:35 UTCEG score recompute
  46. 2026-08-24 19:35 UTCVendor advisory
  47. 2026-08-24 19:35 UTCGHSA enrichment
  48. 2026-08-24 06:29 UTCVendor advisory
  49. 2026-08-24 06:29 UTCGHSA enrichment
  50. 2026-08-23 17:56 UTCVendor advisory
  51. 2026-08-23 17:56 UTCGHSA enrichment
  52. 2026-08-23 05:24 UTCEG score recompute
  53. 2026-08-23 05:24 UTCVendor advisory
  54. 2026-08-23 05:24 UTCGHSA enrichment
  55. 2026-08-23 00:19 UTCEPSS rescore
  56. 2026-08-22 16:51 UTCVendor advisory
  57. 2026-08-22 16:51 UTCGHSA enrichment
  58. 2026-08-22 04:18 UTCEG score recompute
  59. 2026-08-22 04:18 UTCVendor advisory
  60. 2026-08-22 04:18 UTCGHSA enrichment
  61. 2026-08-21 23:49 UTCEPSS rescore
  62. 2026-08-21 15:45 UTCVendor advisory
  63. 2026-08-21 15:45 UTCGHSA enrichment
  64. 2026-08-21 03:12 UTCEG score recompute
  65. 2026-08-21 03:12 UTCVendor advisory
  66. 2026-08-21 03:12 UTCGHSA enrichment
  67. 2026-08-20 22:55 UTCEPSS rescore
  68. 2026-08-20 14:38 UTCVendor advisory
  69. 2026-08-20 14:38 UTCGHSA enrichment
  70. 2026-08-20 00:21 UTCEG score recompute
  71. 2026-08-20 00:21 UTCVendor advisory
  72. 2026-08-20 00:21 UTCGHSA enrichment
  73. 2026-08-19 17:03 UTCEPSS rescore
  74. 2026-08-19 08:36 UTCVendor advisory
  75. 2026-08-19 08:36 UTCGHSA enrichment

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-38755?
CVE-2026-38755 is a high vulnerability published on July 15, 2026. A heap overflow in the evalcommand() function (shell/ash.c) of Busybox v1.38.0 allows attackers to cause a Denial of Service (DoS) via supplying a crafted input.
When was CVE-2026-38755 disclosed?
CVE-2026-38755 was first published in the National Vulnerability Database on July 15, 2026, with the most recent update on July 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-38755 actively exploited?
CVE-2026-38755 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 72.1% of all scored CVEs.
What is the CVSS score of CVE-2026-38755?
CVE-2026-38755 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-38755?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-38755, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-38755

Explore →

Is Your Infrastructure Affected by CVE-2026-38755?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs