{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-39382 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-39382 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-39382 and fix it if it is affected.\n\nWhat it is: 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.\nExploitation: There is no known exploitation of CVE-2026-39382 in the wild and no public exploit code.\n\nAffected product: dbt-labs dbt-core. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-39382/ (Markdown: https://insights.sbomify.com/CVE-2026-39382/index.md)","id":"CVE-2026-39382","markdown":"https://insights.sbomify.com/CVE-2026-39382/index.md","name":"CVE-2026-39382","record":{"aliases":["GHSA-5jxf-vmqr-5g82"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"dbt GitHub Actions","requires_auth":"none","summary":"Attackers can execute arbitrary shell commands in dbt's GitHub Actions workflow by injecting malicious text into issue comment bodies.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-09-05","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-09-05T02:17:39Z","kind":"github_poc","ref":"https://github.com/pvharmo2/gha-lab-4a8fad8536","stars":0,"title":"Security-research lab reproducing CVE-2026-39382 (GHSA-5jxf-vmqr-5g82): command injection in dbt-labs reusable workflow open-issue-in-repo.yml, driven by a dbt-core-style docs-issue.yml caller"}],"tier":"poc_unverified"},"has_fix":false,"headline":"dbt has a Command Injection in Reusable Workflow via Unsanitized comment-body Output","id":"CVE-2026-39382","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Gotenberg unauthenticated blind SSRF via unfiltered webhook URL","id":"CVE-2026-39383"},"packages":[],"prev":{"headline":"Parse Server's Endpoint `/sessions/me` bypasses `_Session` `protectedFields`","id":"CVE-2026-39381"},"products":["dbt-core"],"published":"2026-04-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["dbt-labs"]},"summary":"Attackers can execute arbitrary shell commands in dbt's GitHub Actions workflow by injecting malicious text into issue comment bodies.","url":"https://insights.sbomify.com/CVE-2026-39382/"}