CVE-2026-39382: dbt has a Command Injection in Reusable Workflow via Unsanitized comment-body Output
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.issuecomment.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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
dbt-labs/actionsto a version that resolves this vulnerability.Patch bbed8d28354e9c644c5a7df13946a3a0451f9ab9
Event History
Frequently Asked Questions
What is the severity of CVE-2026-39382?
CVE-2026-39382 has been classified as a high-severity vulnerability due to its potential to allow command injection.
What is the impact of CVE-2026-39382?
CVE-2026-39382 can allow an authenticated user to execute arbitrary commands on the server through unsanitized input.
How do I fix CVE-2026-39382?
To mitigate CVE-2026-39382, ensure that any user inputs in the comment-body are properly sanitized before processing.
Which software versions are affected by CVE-2026-39382?
CVE-2026-39382 affects all versions of dbt-labs/actions that do not implement the necessary input validation.
Is CVE-2026-39382 being actively exploited?
As of now, there are no public reports indicating that CVE-2026-39382 is actively being exploited in the wild.