Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

GHSA-2w46-vq8h-98vh — shopware/core

MEDIUMFix: shopware/shopware@1338dd9

GHSA-2w46-vq8h-98vh is a medium-severity (CVSS 5) vulnerability in shopware/core. A fix is available for shopware/core — see the affected versions and patch details below.

Shopware 6's password recovery link does not expire after email change

Published
Nov 14, 2025
Updated
Sep 10, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected
🐘shopware/core🐘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

Summary

When a customer changes their email address after requesting a password reset, the old password reset link (tied to the previous email) remains valid. An attacker with access to the old email inbox is potentially able to reset the customer’s password even after the user changes their email address.

PoC

  1. Log in to a Shopware account.
  2. Request a password reset for your current email address.
  3. Copy the password reset link but do not open it.
  4. Log back into your account.n
  5. Navigate to Account Settings → Email and change your email address.
  6. Use the previously copied reset link (from before the email change).
  7. The system allows password change using the old link.

Impact

Reproduced on Stable 6.6.10.7 and trunk.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistshopware/coreall versions6.6.10.9composer require shopware/core:^6.6.10.9
🐘Packagistshopware/core≥ 6.7.0.0&&< 6.7.4.16.7.4.1composer require shopware/core:^6.7.4.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update shopware/core to 6.6.10.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2w46-vq8h-98vh is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2w46-vq8h-98vh can be triaged on real exposure rather than presence alone.

Tailored to GHSA-2w46-vq8h-98vh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary When a customer changes their email address after requesting a password reset, the old password reset link (tied to the previous email) remains valid. An attacker with access to the old email inbox is potentially able to reset the customer’s password even after the user changes their email address. ### PoC 1. Log in to a Shopware account. 2. Request a password reset for your current email address. 3. Copy the password reset link but do not open it. 4. Log back into your account.n 5. Navigate to Account Settings → Email and change your email address. 6. Use the previously copied r
O3 Security · Impact-Aware SCA

Is GHSA-2w46-vq8h-98vh in your dependencies?

O3 Security finds GHSA-2w46-vq8h-98vh across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-2w46-vq8h-98vh: shopware/core | O3 Security