# CVE-2026-41249: CoreShop Vulnerable to Remote Code Execution (RCE) via Insecure `pull_request_target` Configuration

> Attackers can execute arbitrary code on CI runners by submitting malicious pull requests due to insecure workflow configuration.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jun 2026
- **Updated:** 8 Jun 2026
- **Also known as:** GHSA-q58j-g3f4-h26h

## What is CVE-2026-41249?

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.

### Official 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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-41249?

2 open source packages ship an affected version, including coreshop/core-shop.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `coreshop/core-shop` | Packagist | All versions | None |
| `coreshop/core-shop` | Packagist | All versions | None |

## How do I fix CVE-2026-41249?

No fix has been published for CVE-2026-41249 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-41249 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41249 exists.

Public exploit code:

- 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 (github_poc): https://github.com/pvharmo2/gha-lab-5bce203f66

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41249 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41249 exists.

Affected packages and fixed versions:
- coreshop/core-shop (Packagist): affected all versions; no fix listed
- coreshop/core-shop (Packagist): affected all versions; no fix listed

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41249/ (Markdown: https://insights.sbomify.com/CVE-2026-41249/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41249
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41249
- OSV: https://osv.dev/vulnerability/CVE-2026-41249

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41249/
Summaries are generated and may contain mistakes; the official description above is the record.