{"answers":{"affected":"2 open source packages ship an affected version, including coreshop/core-shop.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41249 exists.","fix":"No fix has been published for CVE-2026-41249 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-41249 is a high-severity code injection vulnerability in CoreShop, published on 4 Jun 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-41249 and fix it if it is affected.\n\nWhat it is: CVE-2026-41249 is a high-severity code injection vulnerability in CoreShop, published on 4 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41249 exists.\n\nAffected packages and fixed versions:\n- coreshop/core-shop (Packagist): affected all versions; no fix listed\n- coreshop/core-shop (Packagist): affected all versions; no fix listed\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-41249/ (Markdown: https://insights.sbomify.com/CVE-2026-41249/index.md)","id":"CVE-2026-41249","markdown":"https://insights.sbomify.com/CVE-2026-41249/index.md","name":"CVE-2026-41249","record":{"aliases":["GHSA-q58j-g3f4-h26h"],"analysis":{"component_type":"developer_tool","fix_type":"configuration_change","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"GitHub Actions workflow","requires_auth":"none","summary":"Attackers can execute arbitrary code on CI runners by submitting malicious pull requests due to insecure workflow configuration.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"CoreShop is a Pimcore enhanced eCommerce solution. In versions 5.0.1 through 5.1.0-beta.1,, the GitHub Actions workflow (`.github/workflows/static.yml`) uses the `pull_request_target` trigger but dangerously checks out the unverified code from the pull request head (`ref: ${{ github.event.pull_request.head.ref }}`). Subsequently, it executes a script (`bin/console`) from this untrusted checkout. This allows any external attacker to achieve Remote Code Execution (RCE) on the GitHub Actions runner simply by submitting a malicious Pull Request. Also known as a \"Pwn Request\" vulnerability. As of time of publication, `pull_request_target` is still in the file.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":"2026-09-06","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-09-06T21:14:39Z","kind":"github_poc","ref":"https://github.com/pvharmo2/gha-lab-5bce203f66","stars":0,"title":"Security-research lab: reproduction of CVE-2026-41249 (GHSA-q58j-g3f4-h26h) — pull_request_target pwn request in .github/workflows/static.yml, snapshot of coreshop/CoreShop@cc1e3f54"}],"tier":"weaponised"},"has_fix":false,"headline":"CoreShop Vulnerable to Remote Code Execution (RCE) via Insecure `pull_request_target` Configuration","id":"CVE-2026-41249","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"XSS in taiga-front","id":"CVE-2026-41250"},"packages":[{"ecosystem":"Packagist","fixed":[],"introduced":[],"last_affected":[],"package":"coreshop/core-shop","purl":null,"source":"GHSA-q58j-g3f4-h26h"},{"ecosystem":"Packagist","fixed":[],"introduced":[],"last_affected":[],"package":"coreshop/core-shop","purl":"pkg:composer/coreshop/core-shop","source":"GHSA-q58j-g3f4-h26h"}],"prev":{"headline":"Official Clerk JavaScript SDKs: Middleware-based route protection bypass","id":"CVE-2026-41248"},"products":["CoreShop"],"published":"2026-06-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-08","vendors":["coreshop"]},"summary":"Attackers can execute arbitrary code on CI runners by submitting malicious pull requests due to insecure workflow configuration.","url":"https://insights.sbomify.com/CVE-2026-41249/"}