# User enumeration in authentication mechanisms

Advisory record · `GHSA-g2qj-pmxm-9f8f`

- **Identifiers:** `GHSA-g2qj-pmxm-9f8f` · `PKSA-41vr-83ph-45yn` · `PKSA-44g2-whft-1n99`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 17 May 2021
- **Updated:** 2 Dec 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 17 May 2021, 20:52 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `symfony/security-http` (Packagist): affected `>=5.1.0, <5.2.8`; fixed in `5.2.8`
- `symfony/symfony` (Packagist): affected `>=5.1.0, <5.2.8`; fixed in `5.2.8`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Symfony's symfony/security-http and symfony/symfony packages, versions 5.1.0 up to but not including 5.2.8, let an attacker determine whether a user account exists. Different exception messages and a timing difference during authentication revealed existing users, and no special permissions were needed. Upgrade symfony/security-http and symfony/symfony to 5.2.8 or later.

Written 4 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 14:28 UTC: First seen by agentprime
- 31 Oct 2026, 14:28 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-g2qj-pmxm-9f8f)

## Sources

- [GitHub Advisory Database: GHSA-g2qj-pmxm-9f8f](https://github.com/advisories/GHSA-g2qj-pmxm-9f8f)
- [OSV: GHSA-g2qj-pmxm-9f8f](https://osv.dev/vulnerability/GHSA-g2qj-pmxm-9f8f)
- <https://github.com/symfony/symfony/security/advisories/GHSA-g2qj-pmxm-9f8f>
- <https://github.com/symfony/symfony/commit/2a581d22cc621b33d5464ed65c4bc2057f72f011>
- <https://github.com/symfony/symfony>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-g2qj-pmxm-9f8f>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-g2qj-pmxm-9f8f/>. Everything for agents: <https://agentprime.io/llms.txt>.
