CVE-2026-41249

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-05-14. A secondary CVSS source baseline 8.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.2Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
68
EG Risk 68/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity82% × 45%
Exploitation40% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
44th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

June 4, 2026

Last Modified

October 6, 2026

Advisory Details (3)

Auto-updated Jun 4, 2026
Patch available. Sources: github_commit, github.
githubMentions a patch (unverified)

Critical Remote Code Execution (RCE) via Insecure `pull_request_target` Configuration · Advisory · coreshop/CoreShop · GitHub

https://github.com/coreshop/CoreShop/security/advisories/GHSA-q58j-g3f4-h26h
github_commit Patch Available

commit cc1e3f547228 (coreshop/CoreShop)

Patch available: coreshop/CoreShop 5.0.1 (contains commit cc1e3f547228)

https://github.com/coreshop/CoreShop/commit/cc1e3f547228ec5ebfc1dc0472f9a3cc5f4137a4
generic

CoreShop/.github/workflows/static.yml at 5.1.0-beta.1 · coreshop/CoreShop · GitHub

https://github.com/coreshop/CoreShop/blob/5.1.0-beta.1/.github/workflows/static.yml#L14

Vendor Advisories for CVE-2026-41249(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
composercoreshop/core-shop—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
coreshop/core-shop5.0.0——

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 265 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 22:14 UTCEG score recompute
  5. 2026-10-06 22:14 UTCGHSA enrichment
  6. 2026-10-06 15:17 UTCEPSS rescore
  7. 2026-10-05 17:43 UTCEPSS rescore
  8. 2026-10-04 23:22 UTCEPSS rescore
  9. 2026-10-03 14:25 UTCEPSS rescore
  10. 2026-10-03 12:09 UTCOSV refresh
  11. 2026-10-01 19:50 UTCEPSS rescore
  12. 2026-09-30 15:03 UTCEPSS rescore
  13. 2026-09-27 13:48 UTCEPSS rescore
  14. 2026-09-26 15:58 UTCEPSS rescore
  15. 2026-09-23 17:53 UTCEPSS rescore
  16. 2026-09-20 20:15 UTCEPSS rescore
  17. 2026-09-18 19:28 UTCEPSS rescore
  18. 2026-09-17 19:31 UTCEPSS rescore
  19. 2026-09-16 14:08 UTCEPSS rescore
  20. 2026-09-16 05:15 UTCEPSS rescore
  21. 2026-09-14 05:22 UTCEG score recompute
  22. 2026-09-14 05:22 UTCGHSA enrichment
  23. 2026-09-13 16:47 UTCEPSS rescore
  24. 2026-09-12 23:36 UTCOSV refresh
  25. 2026-09-12 15:01 UTCEPSS rescore
Show 75 more
  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-11 09:37 UTCEPSS rescore
  3. 2026-09-10 09:34 UTCEPSS rescore
  4. 2026-09-08 22:00 UTCEPSS rescore
  5. 2026-09-07 16:01 UTCEPSS rescore
  6. 2026-09-06 13:47 UTCEPSS rescore
  7. 2026-09-04 05:06 UTCEPSS rescore
  8. 2026-09-02 14:12 UTCEPSS rescore
  9. 2026-09-01 13:53 UTCEPSS rescore
  10. 2026-09-01 04:39 UTCEPSS rescore
  11. 2026-08-30 19:17 UTCEPSS rescore
  12. 2026-08-30 01:22 UTCEPSS rescore
  13. 2026-08-28 21:41 UTCEPSS rescore
  14. 2026-08-27 14:25 UTCEPSS rescore
  15. 2026-08-26 14:46 UTCEPSS rescore
  16. 2026-08-25 13:49 UTCEPSS rescore
  17. 2026-08-25 03:27 UTCEG score recompute
  18. 2026-08-25 03:27 UTCGHSA enrichment
  19. 2026-08-23 23:52 UTCGHSA enrichment
  20. 2026-08-23 12:41 UTCEG score recompute
  21. 2026-08-23 12:41 UTCGHSA enrichment
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-21 20:10 UTCGHSA enrichment
  25. 2026-08-21 08:34 UTCEG score recompute
  26. 2026-08-21 08:34 UTCGHSA enrichment
  27. 2026-08-20 22:55 UTCEPSS rescore
  28. 2026-08-20 21:19 UTCGHSA enrichment
  29. 2026-08-20 09:56 UTCEG score recompute
  30. 2026-08-20 09:56 UTCGHSA enrichment
  31. 2026-08-19 17:03 UTCEPSS rescore
  32. 2026-08-18 13:48 UTCEPSS rescore
  33. 2026-08-17 14:34 UTCEG score recompute
  34. 2026-08-17 14:34 UTCGHSA enrichment
  35. 2026-08-17 13:47 UTCEPSS rescore
  36. 2026-08-17 03:22 UTCEG score recompute
  37. 2026-08-17 03:22 UTCGHSA enrichment
  38. 2026-08-16 14:56 UTCEPSS rescore
  39. 2026-08-16 14:54 UTCGHSA enrichment
  40. 2026-08-16 02:14 UTCEG score recompute
  41. 2026-08-16 02:14 UTCGHSA enrichment
  42. 2026-08-16 02:14 UTCEPSS rescore
  43. 2026-08-15 14:20 UTCEG score recompute
  44. 2026-08-15 14:20 UTCGHSA enrichment
  45. 2026-08-15 01:30 UTCEPSS rescore
  46. 2026-08-14 21:00 UTCGHSA enrichment
  47. 2026-08-14 09:49 UTCGHSA enrichment
  48. 2026-08-13 22:38 UTCEG score recompute
  49. 2026-08-13 22:38 UTCGHSA enrichment
  50. 2026-08-13 22:00 UTCEPSS rescore
  51. 2026-08-13 07:58 UTCGHSA enrichment
  52. 2026-08-12 20:37 UTCEG score recompute
  53. 2026-08-12 20:37 UTCGHSA enrichment
  54. 2026-08-12 13:51 UTCEPSS rescore
  55. 2026-08-12 09:26 UTCGHSA enrichment
  56. 2026-08-11 22:14 UTCEG score recompute
  57. 2026-08-11 22:14 UTCGHSA enrichment
  58. 2026-08-11 13:43 UTCEPSS rescore
  59. 2026-08-11 10:56 UTCEG score recompute
  60. 2026-08-11 10:56 UTCGHSA enrichment
  61. 2026-08-11 00:00 UTCEPSS rescore
  62. 2026-08-10 23:45 UTCGHSA enrichment
  63. 2026-08-10 12:33 UTCGHSA enrichment
  64. 2026-08-10 01:07 UTCGHSA enrichment
  65. 2026-08-09 13:57 UTCEG score recompute
  66. 2026-08-09 13:57 UTCGHSA enrichment
  67. 2026-08-09 13:46 UTCEPSS rescore
  68. 2026-08-09 02:46 UTCEG score recompute
  69. 2026-08-09 02:46 UTCGHSA enrichment
  70. 2026-08-08 16:37 UTCEPSS rescore
  71. 2026-08-08 15:35 UTCGHSA enrichment
  72. 2026-08-08 04:23 UTCGHSA enrichment
  73. 2026-08-07 17:12 UTCEG score recompute
  74. 2026-08-07 17:12 UTCGHSA enrichment
  75. 2026-08-07 06:01 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-41249?
CVE-2026-41249 is a high vulnerability published on June 4, 2026. 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 pullrequesttarget trigger but dangerously checks out the unverified code from the pull request head (ref: ${{…
When was CVE-2026-41249 disclosed?
CVE-2026-41249 was first published on June 4, 2026, with the most recent update on October 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41249 actively exploited?
CVE-2026-41249 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-41249?
CVE-2026-41249 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-41249?
A fix for CVE-2026-41249 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-41249 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-41249

Explore →

Is Your Infrastructure Affected by CVE-2026-41249?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.