# CVE-2026-49211: Symfony UX: Information exposure via unescaped LIKE wildcards in EntitySearchUtil

> Unescaped LIKE wildcards in Symfony UX autocomplete allow unauthenticated attackers to perform blind boolean oracle attacks and extract data from searchable fields.

- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-946h-jp5c-8fvh

## What is CVE-2026-49211?

CVE-2026-49211 is a medium-severity vulnerability in symfony ux, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Symfony UX is a JavaScript ecosystem for Symfony. From 2.2.0 until 2.36.0 and 3.1.0, Symfony\UX\Autocomplete\Doctrine\EntitySearchUtil::addSearchClause() builds the LIKE expression used by the autocomplete endpoint by wrapping the client-supplied query in %...% without escaping SQL LIKE wildcards (%, _, \), allowing unauthenticated users to turn the public BaseEntityAutocompleteType endpoint into a broad matcher or blind boolean oracle against every column in default searchable_fields. This issue is fixed in versions 2.36.0 and 3.1.0.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-49211?

4 open source packages ship an affected version, including symfony/ux-autocomplete. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `symfony/ux-autocomplete` | Packagist | From 2.2.0 | 2.36.0 |
| `symfony/ux-autocomplete` | Packagist | From 2.2.0 | 2.36.0 |
| `symfony/ux-autocomplete` | Packagist | From 3.0.0 | 3.1.0 |
| `symfony/ux-autocomplete` | Packagist | From 3.0.0 | 3.1.0 |

Products: Symfony Ux.

## How do I fix CVE-2026-49211?

Upgrade symfony/ux-autocomplete to a fixed version for your release line: 2.36.0 or 3.1.0.

## Is CVE-2026-49211 being exploited?

There is no known exploitation of CVE-2026-49211 in the wild and no public exploit code.

## Other vulnerabilities in symfony ux

- [CVE-2026-49208](https://insights.sbomify.com/CVE-2026-49208/): Symfony UX: Format-less date LiveProps parsed with the permissive DateTime constructor (medium 6.9)
- [CVE-2026-49212](https://insights.sbomify.com/CVE-2026-49212/): Symfony UX: LiveComponentHydrator HMAC checksum lacks component and slot binding (medium 6.9)
- [CVE-2026-55877](https://insights.sbomify.com/CVE-2026-55877/): Symfony UX: XSS in symfony/ux-icons via unsanitized SVG content in local files and Iconify on-demand responses (medium 6.1)
- [CVE-2026-49209](https://insights.sbomify.com/CVE-2026-49209/): Symfony UX: Denial of service in symfony/ux-live-component via unbounded batch action requests (medium 5.3)
- [CVE-2026-49216](https://insights.sbomify.com/CVE-2026-49216/): Symfony UX: XSS in symfony/ux-autocomplete via unescaped AJAX response data (medium 5.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-49211 and fix it if it is affected.

What it is: CVE-2026-49211 is a medium-severity vulnerability in symfony ux, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-49211 in the wild and no public exploit code.

Affected packages and fixed versions:
- symfony/ux-autocomplete (Packagist): affected from 2.2.0; fixed in 2.36.0
- symfony/ux-autocomplete (Packagist): affected from 2.2.0; fixed in 2.36.0
- symfony/ux-autocomplete (Packagist): affected from 3.0.0; fixed in 3.1.0
- symfony/ux-autocomplete (Packagist): affected from 3.0.0; fixed in 3.1.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-49211/ (Markdown: https://insights.sbomify.com/CVE-2026-49211/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-49211
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-49211
- OSV: https://osv.dev/vulnerability/CVE-2026-49211

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-49211/
Summaries are generated and may contain mistakes; the official description above is the record.