How severe is GHSA-5pv8-ppvj-4h68?

GHSA-5pv8-ppvj-4h68 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-5pv8-ppvj-4h68?

GHSA-5pv8-ppvj-4h68 affects the following packages: symfony/security (Packagist), symfony/security-guard (Packagist), symfony/security-guard (Packagist), symfony/security-guard (Packagist), symfony/security-core (Packagist), symfony/security-core (Packagist), symfony/security-core (Packagist), lexik/jwt-authentication-bundle (Packagist), and 9 more. Ecosystems affected: Packagist.

How do I fix GHSA-5pv8-ppvj-4h68?

Update symfony/security to 5.2.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5pv8-ppvj-4h68 is resolved across your whole dependency graph.

How do I detect GHSA-5pv8-ppvj-4h68 in my Packagist dependencies?

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

How do I mitigate GHSA-5pv8-ppvj-4h68 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-5pv8-ppvj-4h68 actively exploited in the wild?

No public exploit code has been indexed for GHSA-5pv8-ppvj-4h68 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-5pv8-ppvj-4h68?

GHSA-5pv8-ppvj-4h68 has an EPSS (Exploit Prediction Scoring System) score of 1.6%, placing it in the 77th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-5pv8-ppvj-4h68?

GHSA-5pv8-ppvj-4h68 is classified as Information Exposure (CWE-200), CWE-203 (CWE-203). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-5pv8-ppvj-4h68 published, and has it been updated?

GHSA-5pv8-ppvj-4h68 was published on May 13, 2021 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

Prevent user enumeration using Guard or the new Authenticator-based SecurityGHSA-5pv8-ppvj-4h68

MEDIUMFix: symfony/symfony@2a581d2

GHSA-5pv8-ppvj-4h68 is a medium-severity (CVSS 5.3) Information Exposure vulnerability in symfony/security. A fix is available for symfony/security — see the affected versions and patch details below.

Also known asBIT-symfony-2021-21424CVE-2021-21424

Published

May 13, 2021

Updated

Sep 10, 2026

Affected

17 pkgs

Patched

17 / 17

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs77th percentile — riskier than 77% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

17 pkgs affected

🐘symfony/security🐘symfony/security-guard🐘symfony/security-guard🐘symfony/security-guard🐘symfony/security-core🐘symfony/security-core🐘symfony/security-core🐘lexik/jwt-authentication-bundle+9 more

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

The ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.

Resolution

We now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.

The patch for this issue is available here for branch 3.4.

Credits

I would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.

Affected Packages

17 total 17 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`symfony/security`	≥ 5.0.0&&< 5.2.8	5.2.8`composer require symfony/security:^5.2.8`
🐘Packagist	`symfony/security-guard`	≥ 2.8.0&&< 3.4.48	3.4.48`composer require symfony/security-guard:^3.4.48`
🐘Packagist	`symfony/security-guard`	≥ 4.0.0&&< 4.4.23	4.4.23`composer require symfony/security-guard:^4.4.23`
🐘Packagist	`symfony/security-guard`	≥ 5.0.0&&< 5.2.8	5.2.8`composer require symfony/security-guard:^5.2.8`
🐘Packagist	`symfony/security-core`	≥ 2.8.0&&< 3.4.48	3.4.48`composer require symfony/security-core:^3.4.48`
🐘Packagist	`symfony/security-core`	≥ 4.0.0&&< 4.4.23	4.4.23`composer require symfony/security-core:^4.4.23`

Affected Products

2 products · 5 configurations

fedorafedoraproject

2 versions

3334

Application

symfonysensiolabs

≥ 5.0.0 && < 5.2.8

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symfony/security, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update symfony/security to 5.2.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5pv8-ppvj-4h68 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

Description ----------- The ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user. Resolution ---------- We now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist. The patch for this issue is available [here](https://github.com/symfony/symfony/commit/2a581d22cc621

O3 Security · Impact-Aware SCA

Is GHSA-5pv8-ppvj-4h68 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

Prevent user enumeration using Guard or the new Authenticator-based SecurityGHSA-5pv8-ppvj-4h68

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Description

Resolution

Credits

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-5pv8-ppvj-4h68 in your dependencies?