# symfony/ux-autocomplete: Information exposure via unescaped LIKE wildcards in EntitySearchUtil

Advisory record · `GHSA-946h-jp5c-8fvh`

- **Identifiers:** `GHSA-946h-jp5c-8fvh` · `CVE-2026-49211` · `PKSA-msh7-gxqk-k56q`
- **State:** Confirmed
- **Severity:** CVSS 6.9 Medium
- **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:** 19 Jun 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 19 Jun 2026, 19:34 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `symfony/ux-autocomplete` (Packagist): affected `>=2.2.0, <2.36.0 || >=3.0.0, <3.1.0`; fixed in `2.36.0`, `3.1.0`

## Machine-written summary

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

> The symfony/ux-autocomplete Packagist package is affected in versions from 2.2.0 before 2.36.0 and from 3.0.0 before 3.1.0. Its Doctrine search helper wraps the client's query in LIKE wildcards without escaping them, so a client can use % or \_ to match rows in unintended ways. An unauthenticated user can exploit this when the autocomplete endpoint is public, using the wildcards to broadly match or probe entity columns the application did not mean to expose; the source does not describe SQL injection. Upgrade to 2.36.0 or 3.1.0, which escape these characters.

Written 31 Oct 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

- 6.9 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0053, the 45th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:01 UTC: First seen by agentprime
- 31 Oct 2026, 14:01 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-946h-jp5c-8fvh)

## Sources

- [GitHub Advisory Database: GHSA-946h-jp5c-8fvh](https://github.com/advisories/GHSA-946h-jp5c-8fvh)
- [OSV: GHSA-946h-jp5c-8fvh](https://osv.dev/vulnerability/GHSA-946h-jp5c-8fvh)
- <https://github.com/symfony/ux/security/advisories/GHSA-946h-jp5c-8fvh>
- <https://github.com/symfony/ux/commit/725ab3d40689c91ff19ad2d01940a30007769214>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/ux-autocomplete/CVE-2026-49211.yaml>
- <https://github.com/symfony/ux>

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-946h-jp5c-8fvh>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-946h-jp5c-8fvh/>. Everything for agents: <https://agentprime.io/llms.txt>.
