CoreShop Vulnerable to Remote Code Execution (RCE) via Insecure pull_request_target Configuration

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.2 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

EPSS

• CVE-2026-41249: 0.55% estimated exploitation activity in the next 30 days; percentile 46.01 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The GitHub Actions workflow (.github/workflows/static.yml) uses the pullrequesttarget trigger but dangerously checks out the unverified code from the pull request head (ref: ${{ github.event.pullrequest.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. Steps to Reproduce: 1. Fork the target repository. 2. In the forked repository, modify a file that satisfies the paths condition (e.g., src/dummy.php or composer.json) to trigger the workflow. 3. Modify the bin/console file (which is executed in the workflow steps) with the following malicious payload: 4. Commit the changes and open a Pull Request against the 5.0 or next branch of the base repository. 5. The Static Tests workflow will trigger automatically. Navigate to the Actions tab and…

Published by the source

14 May 2026, 13:18 UTC

Last modified by the source

9 Jun 2026, 11:55 UTC

Source last checked

26 Oct 2026, 14:48 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-q58j-g3f4-h26h

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-41249

Advisory: CoreShop Vulnerable to Remote Code Execution (RCE) via Insecure `pull_request_target` Configuration
IDs: CVE-2026-41249, GHSA-q58j-g3f4-h26h
Record: https://patchnext.com/advisories/cve-2026-41249 (revision 1, source checked 26 Oct 2026, 14:48 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist coreshop/core-shop: affected >= 5.0.0, <= 5.0.0

## Suggested inspection (read-only)
- Packagist coreshop/core-shop: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on coreshop/core-shop.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-q58j-g3f4-h26h (GitHub-reviewed advisory GHSA-q58j-g3f4-h26h lists affected ranges: Packagist coreshop/core-shop >=5.0.0 <=5.0.0)

Commands are suggestions: review each one before running it.