CVE-2026-39382 is a command injection vulnerability in the reusable GitHub Actions workflow dbt-labs/actions/.github/workflows/open-issue-in-repo.yml. In the prep job, the workflow uses peter-evans/find-comment to locate an existing comment indicating that a docs issue has already been opened. The resulting steps.issue_comment.outputs.comment-body value is attacker-controlled and is interpolated directly into a Bash if statement without proper escaping or neutralization. A malicious comment body can break out of the intended quoted string context and inject arbitrary shell commands for execution within the workflow runner environment.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
open-issue-in-repo.yml in untrusted contexts where attacker-controlled comment content can reach the prep job. Do not interpolate untrusted workflow outputs into shell commands or conditionals without strict escaping or safer handling. Where possible, restrict workflow triggers, reduce token and secret exposure to the job, and limit permissions available to the workflow runner.Patch, then assume compromise.
bbed8d28354e9c644c5a7df13946a3a0451f9ab9. Replace vulnerable workflow definitions with the patched implementation so that attacker-controlled comment content is no longer interpolated into shell syntax unsafely.No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.