GHSA-vvmr-8829-6whx is a high-severity (CVSS 8.1) Cross-Site Request Forgery (CSRF) vulnerability in symfony/framework-bundle. O3 Security confirms whether GHSA-vvmr-8829-6whx is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
CSRF token missing in Symfony
Real-World Exposure
symfony/framework-bundle🐘symfony/framework-bundle🐘symfony/framework-bundleReal-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
Description
The Symfony form component provides a CSRF protection mechanism by using a random token injected in the form and using the session to store and control the token submitted by the user. When using the FrameworkBundle, this protection can be enabled or disabled with the configuration. If the configuration is not specified, by default, the mechanism is enabled as long as the session is enabled.
In a recent change in the way the configuration is loaded, the default behavior has been dropped and, as a result, the CSRF protection is not enabled in form when not explicitly enabled, which makes the application sensible to CSRF attacks.
Resolution
Symfony restored the default configuration to enable the CSRF protection by default.
The patch for this issue is available here for branch 5.3.
Credits
We would like to thank Catalin Dan and David Lochner for reporting the issue and Jérémy Derussé for fixing the issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | symfony/framework-bundle | ≥ 5.3.14&&< 5.3.15 | 5.3.15 |
| 🐘Packagist | symfony/framework-bundle | ≥ 5.4.3&&< 5.4.4 | 5.4.4 |
| 🐘Packagist | symfony/framework-bundle | ≥ 6.0.3&&< 6.0.4 | 6.0.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symfony/framework-bundle. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update symfony/framework-bundle to 5.3.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vvmr-8829-6whx 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 pinpoints whether GHSA-vvmr-8829-6whx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-vvmr-8829-6whx. 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-vvmr-8829-6whx in your dependencies?
O3 detects GHSA-vvmr-8829-6whx across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.