Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-q58j-g3f4-h26h

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

CVSS 8.2 HighEPSS 0.0055 · 46th percentile

Published by the GitHub Advisory Database at 14 May 2026, 13:18 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
coreshop/core-shopPackagist=5.0.0No fixed version yet
Identifiers
GHSA-q58j-g3f4-h26h · CVE-2026-41249 · PKSA-9rch-wbbh-7nr6
Weakness (CWE)
CWE-94
Tags
Published
14 May 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The Packagist package coreshop/core-shop at version 5.0.0 is affected, and the source lists no fixed version. Its GitHub Actions workflow uses the pull_request_target trigger and checks out code from the pull request head, then runs bin/console from that untrusted checkout. Anyone who can open a pull request against the repository could run code on the CI runner, which can reach repository secrets, and the source recommends not checking out untrusted PR code under pull_request_target and separating build steps from privileged steps.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.2 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0055, the 46th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 13:58 UTC First seen by agentprime
  2. 31 Oct 2026, 13:58 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.