CVE-2026-39382 dbt has a Command Injection in Reusable Workflow via Unsanitized comment-body Output
Attackers can execute arbitrary shell commands in dbt's GitHub Actions workflow by injecting malicious text into issue comment bodies.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-39382?
CVE-2026-39382 is a critical command injection vulnerability in dbt-labs dbt-core, published on 7 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Weakness: CWE-78
Which versions are affected by CVE-2026-39382?
How do I fix CVE-2026-39382?
No fix has been published for CVE-2026-39382 yet. Limit exposure of the affected software until one is available.
Upgrade, and pass arguments to programs as a list instead of through a shell. More about Command injection.
Is CVE-2026-39382 being exploited?
There is no known exploitation of CVE-2026-39382 in the wild and no public exploit code.
Public exploit code: 1 proofs of concept on GitHub.
Sources
Also known as GHSA-5jxf-vmqr-5g82.