How severe is GHSA-7cw6-7h3h-v8pf?

GHSA-7cw6-7h3h-v8pf has a CVSS score of 7.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-7cw6-7h3h-v8pf?

GHSA-7cw6-7h3h-v8pf affects the following packages: shopware/shopware (Packagist), shopware/core (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-7cw6-7h3h-v8pf?

Update shopware/shopware to 6.7.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7cw6-7h3h-v8pf is resolved across your whole dependency graph.

How do I detect GHSA-7cw6-7h3h-v8pf in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for shopware/shopware, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-7cw6-7h3h-v8pf if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is GHSA-7cw6-7h3h-v8pf actively exploited in the wild?

No public exploit code has been indexed for GHSA-7cw6-7h3h-v8pf yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-7cw6-7h3h-v8pf?

GHSA-7cw6-7h3h-v8pf has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 39th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-7cw6-7h3h-v8pf?

GHSA-7cw6-7h3h-v8pf is classified as Code Injection (CWE-94). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-7cw6-7h3h-v8pf published, and has it been updated?

GHSA-7cw6-7h3h-v8pf was published on January 14, 2026 and was last updated on February 3, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

HIGH severity

Shopware Has Improper Control of Generation of Code in Twig rendered viewsGHSA-7cw6-7h3h-v8pf

HIGHFix: shopware/shopware@3966b05

GHSA-7cw6-7h3h-v8pf is a high-severity (CVSS 7.2) Code Injection vulnerability in shopware/shopware. A fix is available for shopware/shopware — see the affected versions and patch details below.

Also known asCVE-2026-23498

Published

Jan 14, 2026

Updated

Feb 3, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-7cw6-7h3h-v8pf.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs39th percentile — riskier than 39% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

🐘shopware/shopware🐘shopware/core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Impact

We fixed with CVE-2023-2017 Twig filters to only be executed with allowed functions. However there was a regression that lead to an array and array crafted PHP Closure not checked being against allow list for the map(...) override

Patches

Patched in 6.7.6.1

Workarounds

Install the security plugin

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`shopware/shopware`	≥ 6.7.0.0&&< 6.7.6.1	6.7.6.1`composer require shopware/shopware:^6.7.6.1`
🐘Packagist	`shopware/core`	≥ 6.7.0.0&&< 6.7.6.1	6.7.6.1`composer require shopware/core:^6.7.6.1`

Affected Products

1 product · 1 configurations

Application

shopwareshopware

≥ 6.7.0.0 && < 6.7.6.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for shopware/shopware, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update shopware/shopware to 6.7.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7cw6-7h3h-v8pf is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

### Impact We fixed with [CVE-2023-2017](https://github.com/advisories/GHSA-7v2v-9rm4-7m8f) Twig filters to only be executed with allowed functions. However there was a regression that lead to an array and array crafted PHP Closure not checked being against allow list for the map(...) override ### Patches Patched in 6.7.6.1 ### Workarounds Install the security plugin