{"answers":{"affected":"1 open source package ship an affected version, including j178/prek-action.","exploited":"There is no known exploitation of GHSA-pwf7-47c3-mfhx in the wild and no public exploit code.","fix":"Upgrade j178/prek-action to 1.0.6 or later.","what":"GHSA-pwf7-47c3-mfhx is a code injection vulnerability in j178/prek-action, published on 29 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-pwf7-47c3-mfhx and fix it if it is affected.\n\nWhat it is: GHSA-pwf7-47c3-mfhx is a code injection vulnerability in j178/prek-action, published on 29 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-pwf7-47c3-mfhx in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- j178/prek-action (GitHub Actions): affected all versions; fixed in 1.0.6\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/GHSA-pwf7-47c3-mfhx/ (Markdown: https://insights.sbomify.com/GHSA-pwf7-47c3-mfhx/index.md)","id":"GHSA-pwf7-47c3-mfhx","markdown":"https://insights.sbomify.com/GHSA-pwf7-47c3-mfhx/index.md","name":"GHSA-pwf7-47c3-mfhx","record":{"aliases":[],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"GitHub Actions","requires_auth":"none","summary":"Attackers can inject arbitrary code via action inputs to execute commands and steal secrets in GitHub Actions workflows.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Summary\nThere are three potential attacks of arbitrary code injection vulnerability in the composite action at _action.yml_.\n\n### Details\nThe GitHub Action variables `inputs.prek-version`, `inputs.extra_args`, and `inputs.extra-args` can be used to execute arbitrary code in the context of the action.\n\n### PoC\n```yaml\n- uses: j178/prek-action@v1.0.5\n  with:\n    prek-version: $(printenv \u003e\u003e $GITHUB_STEP_SUMMARY \u0026\u0026 echo \"0.2.2\")\n    extra_args: '\u0026\u0026 echo \"MY_SECRET with a character is: ${MY_SECRET:0:1}a${MY_SECRET:1}\" \u003e\u003e $GITHUB_STEP_SUMMARY \u0026\u0026 echo \"\"'\n  env:\n    MY_SECRET: ${{ secrets.MY_SECRET }}\n```\n\nThe previous example will print all the environment variables, and it will expose `MY_SECRET` environment variable value to the summary of the workflow. An attacker could potentially use this vector to compromise the security of the target repository, even passing unnotice because the action will run normally.\n\n### Impact\nCritical, CWE-94","ecosystems":["GitHub Actions"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"j178/prek-action vulnerable to arbitrary code injection in composite action","id":"GHSA-pwf7-47c3-mfhx","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"GitHub Actions","product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"GitHub Actions","fixed":["1.0.6"],"introduced":["0"],"last_affected":[],"package":"j178/prek-action","purl":null,"source":"GHSA-pwf7-47c3-mfhx"}],"products":null,"published":"2025-09-29","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can inject arbitrary code via action inputs to execute commands and steal secrets in GitHub Actions workflows.","url":"https://insights.sbomify.com/GHSA-pwf7-47c3-mfhx/"}