CVE-2026-39382

CRITICALNVD 9.39.3—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.3 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 94% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.3
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.3Exploit: NoneExposed: 0

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

dbt enables data analysts and engineers to transform their data using the same practices that software engineers use to build applications. Inside the reusable workflow dbt-labs/actions/blob/main/.github/workflows/open-issue-in-repo.yml, the prep job uses peter-evans/find-comment to search for an existing comment indicating that a docs issue has already been opened. The output steps.issue_comment.outputs.comment-body is then interpolated directly into a bash if statement. Because comment-body is attacker-controlled text and is inserted into shell syntax without escaping, a malicious comment body can break out of the quoted string and inject arbitrary shell commands. This vulnerability is fixed with commit bbed8d28354e9c644c5a7df13946a3a0451f9ab9.

CVSS v3
9.3
EG Score
9.3(medium)
EPSS
31.1%
KEV
Not listed

Published

April 7, 2026

Last Modified

April 16, 2026

Advisory Details (2)

Auto-updated Jun 7, 2026
Patch available. Sources: github_commit, github.
github Patch Available

Command Injection in Reusable Workflow via Unsanitized comment-body Output · Advisory · dbt-labs/dbt-core · GitHub

https://github.com/dbt-labs/dbt-core/security/advisories/GHSA-5jxf-vmqr-5g82
github_commit

commit bbed8d28354e (dbt-labs/actions)

Fix landed in dbt-labs/actions commit bbed8d28354e — awaiting tagged release

https://github.com/dbt-labs/actions/commit/bbed8d28354e9c644c5a7df13946a3a0451f9ab9

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 37× 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 101 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-39382?
CVE-2026-39382 is a critical vulnerability published on April 7, 2026. dbt enables data analysts and engineers to transform their data using the same practices that software engineers use to build applications. Inside the reusable workflow dbt-labs/actions/blob/main/.github/workflows/open-issue-in-repo.yml, the prep job uses peter-evans/find-comment to search for an…
When was CVE-2026-39382 disclosed?
CVE-2026-39382 was first published in the National Vulnerability Database on April 7, 2026, with the most recent update on April 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-39382 actively exploited?
CVE-2026-39382 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 31.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-39382?
CVE-2026-39382 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2026-39382?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-39382, 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-39382

Explore →

Is Your Infrastructure Affected by CVE-2026-39382?

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

Start Free Scan →Browse All CVEs