CVE-2026-41010

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-06-04. a secondary CVSS source baseline 8.2; sources differ by 0.0.

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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

ReleaseJob#unpack builds job_dir = File.join(@release_dir, 'jobs', name) and job_tgz = File.join(@release_dir, 'jobs', "#{name}.tgz") where name returns @job_meta['name'], a value taken verbatim from the jobs: array of the attacker-supplied release.MF inside the uploaded tarball. These paths are then interpolated into a shell string: Bosh::Common::Exec.sh("tar -C #{job_dir} -xf #{job_tgz} 2>&1", :on_error => :return). Bosh::Common::Exec.sh executes via %x{#{command}} (bosh-common/lib/bosh/common/exec.rb:53), i.e. /bin/sh -c, so any shell metacharacters in name are interpreted. FileUtils.mkdir_p(job_dir) on line 49 creates the literal directory (no shell) and succeeds even when the name contains $()/;, so execution reaches the sh call.

Affected versions:

  • BOSH Director: all versions prior to v282.1.12 (inclusive); fixed in v282.1.12 or later

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity82% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

June 4, 2026

Last Modified

July 22, 2026

Advisory Details (1)

Auto-updated Jun 4, 2026
No patch confirmed yet.
generic

CVE-2026-41010 - Release Job Name Command Injection on BOSH Director | Cloud Foundry

https://www.cloudfoundry.org/blog/cve-2026-41010-release-job-name-command-injection-on-bosh-director/

Vendor Advisories for CVE-2026-41010(1)

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

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 45× 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 122 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-41010?
CVE-2026-41010 is a high vulnerability published on June 4, 2026. ReleaseJob#unpack builds jobdir = File.join(@releasedir, 'jobs', name) and jobtgz = File.join(@releasedir, 'jobs', "#{name}.tgz") where name returns @jobmeta['name'], a value taken verbatim from the jobs: array of the attacker-supplied release.MF inside the uploaded tarball. These paths are then…
When was CVE-2026-41010 disclosed?
CVE-2026-41010 was first published in the National Vulnerability Database on June 4, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41010 actively exploited?
CVE-2026-41010 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 97.6% of all scored CVEs.
What is the CVSS score of CVE-2026-41010?
CVE-2026-41010 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-41010?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41010, 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

Explore the affected products and dependency analysis for CVE-2026-41010

Explore →

Is Your Infrastructure Affected by CVE-2026-41010?

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

Start Free Scan →Browse All CVEs