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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.3 · CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-49211: 0.53% estimated exploitation activity in the next 30 days; percentile 44.96 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Description Symfony\UX\Autocomplete\Doctrine\EntitySearchUtil::addSearchClause() builds the LIKE expression used by the autocomplete endpoint by wrapping the client-supplied query in %...% without escaping the SQL LIKE wildcards (%, , \). The value is passed as a bound parameter, so this is not SQL injection, but a client can send % to match every row or use as a single-character wildcard. Because searchablefields defaults to every property of the entity and the autocomplete endpoint is public by default (BaseEntityAutocompleteType ships with security = false), an unauthenticated user can turn the endpoint into a broad matcher or a blind boolean oracle against every column of the entity, including columns the application never intended to expose. Resolution EntitySearchUtil now escapes \, %, and in the user-supplied query with addcslashes() and appends an explicit ESCAPE '\' clause to the generated LIKE expression, so those characters are matched literally. The exact-match wordsquery…

Published by the source

19 Jun 2026, 19:34 UTC

Last modified by the source

19 Jun 2026, 19:34 UTC

Source last checked

26 Oct 2026, 14:49 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-946h-jp5c-8fvh

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-49211

Advisory: symfony/ux-autocomplete: Information exposure via unescaped LIKE wildcards in EntitySearchUtil
IDs: CVE-2026-49211, GHSA-946h-jp5c-8fvh
Record: https://patchnext.com/advisories/cve-2026-49211 (revision 1, source checked 26 Oct 2026, 14:49 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: symfony/ux-autocomplete 3.1.0, 2.36.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist symfony/ux-autocomplete: affected >= 2.2.0, < 2.36.0; >= 3.0.0, < 3.1.0; fixed in 3.1.0, 2.36.0

## Suggested inspection (read-only)
- Packagist symfony/ux-autocomplete: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on symfony/ux-autocomplete.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-946h-jp5c-8fvh (GitHub-reviewed advisory GHSA-946h-jp5c-8fvh lists affected ranges: Packagist symfony/ux-autocomplete >=2.2.0 =3.0.0 <3.1.0)

Commands are suggestions: review each one before running it.