GHSA-9wg9-93h9-j8ch is a critical-severity (CVSS 9.1) vulnerability in auth0/symfony. A fix is available for auth0/symfony — see the affected versions and patch details below.
Auth0 Symfony SDK Vulnerable to Brute Force Authentication Tags of CookieStore Sessions
Real-World Exposure
auth0/symfonyReal-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
Overview Session cookies of applications using the Auth0 symfony SDK configured with CookieStore have authentication tags that can be brute forced, which may result in unauthorized access.
Am I Affected? You are affected by this vulnerability if you meet the following pre-conditions:
- Applications using the Auth0 symfony SDK with version <=5.3.1
- Auth0/Symfony SDK uses the Auth0-PHP SDK with version 8.0.0-BETA1 or higher and below 8.14.0.
- Session storage configured with CookieStore.
Fix Upgrade Auth0/symfony to v5.4.0. As an additional precautionary measure, we recommend rotating your cookie encryption keys. Note that once updated, any previous session cookies will be rejected.
Acknowledgement Okta would like to thank Félix Charette for discovering this vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | auth0/symfony | all versions | 5.4.0composer require auth0/symfony:^5.4.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for auth0/symfony, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update auth0/symfony to 5.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9wg9-93h9-j8ch is resolved across your whole dependency graph.
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-9wg9-93h9-j8ch can be triaged on real exposure rather than presence alone.
Tailored to GHSA-9wg9-93h9-j8ch. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-9wg9-93h9-j8ch in your dependencies?
O3 Security finds GHSA-9wg9-93h9-j8ch across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.