Shopware's session is persistent in Cache for 404 pages

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

EPSS

• CVE-2024-27917: 0.61% estimated exploitation activity in the next 30 days; percentile 49.34 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact The Symfony Session Handler, pop's the Session Cookie and assign it to the Response. Since Shopware 6.5.8.0 the 404 pages, are cached, to improve the performance of 404 pages. So the cached Response, contains a Session Cookie when the Browser accessing the 404 page, has no cookies yet. The Symfony Session Handler is in use, when no explicit Session configuration has been done. When Redis is in use for Sessions using the PHP Redis extension, this exploiting code is not used. Patches Update to Shopware version 6.5.8.7 Workarounds Using Redis for Sessions, as this does not trigger the exploit code. Example configuration for Redis Consequences As an guest browser session has been cached on a 404 page, every missing image or directly reaching a 404 page will logout the customer or clear his cart.

Published by the source

6 Mar 2024, 15:06 UTC

Last modified by the source

17 Feb 2026, 22:02 UTC

Source last checked

26 Oct 2026, 14:38 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-c2f9-4jmm-v45m

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-27917

Advisory: Shopware's session is persistent in Cache for 404 pages
IDs: CVE-2024-27917, GHSA-c2f9-4jmm-v45m
Record: https://patchnext.com/advisories/cve-2024-27917 (revision 1, source checked 26 Oct 2026, 14:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: shopware/storefront 6.5.8.7; shopware/platform 6.5.8.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist shopware/storefront: affected >= 6.5.8.0, < 6.5.8.7; fixed in 6.5.8.7
- Packagist shopware/platform: affected >= 6.5.8.0, < 6.5.8.7; fixed in 6.5.8.7

## Suggested inspection (read-only)
- Packagist shopware/storefront: check the installed version with your package manager.
- Packagist shopware/platform: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on shopware/storefront, shopware/platform.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-c2f9-4jmm-v45m (GitHub-reviewed advisory GHSA-c2f9-4jmm-v45m lists affected ranges: Packagist shopware/storefront >=6.5.8.0 =6.5.8.0 <6.5.8.7)

Commands are suggestions: review each one before running it.