GHSA-q87v-q8fw-gmj5 is a critical-severity (CVSS 9.8) CWE-284 vulnerability in symfony/security-core. A fix is available for symfony/security-core — see the affected versions and patch details below.
Symfony Incorrect Access Control
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-q87v-q8fw-gmj5 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
symfony/security-core🐘symfony/security-core🐘symfony/security-core🐘symfony/security-core🐘symfony/security🐘symfony/security🐘symfony/security🐘symfony/security+4 moreReal-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
Certain Symfony products are affected by: Incorrect Access Control. This affects Symfony 2.7.30 and Symfony 2.8.23 and Symfony 3.2.10 and Symfony 3.3.3. The type of exploitation is: remote. The component is: Password validator.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | symfony/security-core | ≥ 2.7.30&&< 2.7.32 | 2.7.32composer require symfony/security-core:^2.7.32 |
| 🐘Packagist | symfony/security-core | ≥ 2.8.23&&< 2.8.25 | 2.8.25composer require symfony/security-core:^2.8.25 |
| 🐘Packagist | symfony/security-core | ≥ 3.2.10&&< 3.2.12 | 3.2.12composer require symfony/security-core:^3.2.12 |
| 🐘Packagist | symfony/security-core | ≥ 3.3.3&&< 3.3.5 | 3.3.5composer require symfony/security-core:^3.3.5 |
| 🐘Packagist | symfony/security | ≥ 2.7.30&&< 2.7.32 | 2.7.32composer require symfony/security:^2.7.32 |
| 🐘Packagist | symfony/security | ≥ 2.8.23&&< 2.8.25 | 2.8.25composer require symfony/security:^2.8.25 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symfony/security-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update symfony/security-core to 2.7.32 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q87v-q8fw-gmj5 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-q87v-q8fw-gmj5 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-q87v-q8fw-gmj5. 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-q87v-q8fw-gmj5 in your dependencies?
O3 Security finds GHSA-q87v-q8fw-gmj5 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.