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
Elevated
8.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.2Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.2(medium)
EG Risk
68(Attend)
EG Risk 68/100SSVC: Attend

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%
Action: Remediate soon — notable exploitation risk.
EPSS
35.4%
KEV
Not listed

Published

June 4, 2026

Last Modified

July 22, 2026

Advisory Details (3)

Auto-updated Jun 4, 2026
Patch available. Sources: github_commit, github.
github Patch Available

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 / EcosystemFixed in / PatchReleasedSource
composercoreshop/core-shopghsa

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 rangeFixed inDependents
coreshop/core-shop5.0.0

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 61× 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 124 total refreshes for this CVE.

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

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 in the National Vulnerability Database on June 4, 2026, with the most recent update on July 22, 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 35.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41249?
CVE-2026-41249 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-41249?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41249, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.