How severe is GHSA-946h-jp5c-8fvh?

No CVSS score has been assigned to GHSA-946h-jp5c-8fvh yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-946h-jp5c-8fvh?

GHSA-946h-jp5c-8fvh affects the following packages: symfony/ux-autocomplete (Packagist), symfony/ux-autocomplete (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-946h-jp5c-8fvh?

Update symfony/ux-autocomplete to 2.36.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-946h-jp5c-8fvh is resolved across your whole dependency graph.

How do I detect GHSA-946h-jp5c-8fvh in my Packagist dependencies?

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

How do I mitigate GHSA-946h-jp5c-8fvh if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is GHSA-946h-jp5c-8fvh actively exploited in the wild?

No public exploit code has been indexed for GHSA-946h-jp5c-8fvh 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-946h-jp5c-8fvh?

GHSA-946h-jp5c-8fvh has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 44th 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-946h-jp5c-8fvh?

GHSA-946h-jp5c-8fvh is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-946h-jp5c-8fvh published, and has it been updated?

GHSA-946h-jp5c-8fvh was published on June 19, 2026 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

symfony/ux-autocomplete: Information exposure via unescaped LIKE wildcards in EntitySearchUtilGHSA-946h-jp5c-8fvh

Fix: symfony/ux@725ab3d

GHSA-946h-jp5c-8fvh is a Information Exposure vulnerability in symfony/ux-autocomplete. A fix is available for symfony/ux-autocomplete — see the affected versions and patch details below.

Also known asCVE-2026-49211

Published

Jun 19, 2026

Updated

Sep 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-946h-jp5c-8fvh.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs44th percentile — riskier than 44% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs affected

🐘symfony/ux-autocomplete🐘symfony/ux-autocomplete

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

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 searchable_fields 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 words_query IN() branch is unchanged.

The patch for this issue is available here for branch 2.x (and forward-ported to 3.x).

Credits

Symfony would like to thank Pascal Cescon for reporting the issue and providing the fix.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`symfony/ux-autocomplete`	≥ 2.2.0&&< 2.36.0	2.36.0`composer require symfony/ux-autocomplete:^2.36.0`
🐘Packagist	`symfony/ux-autocomplete`	≥ 3.0.0&&< 3.1.0	3.1.0`composer require symfony/ux-autocomplete:^3.1.0`

Affected Products

1 product · 2 configurations

Application

uxsymfony

≥ 2.2.0 && < 2.36.0

1 version

3.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symfony/ux-autocomplete, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update symfony/ux-autocomplete to 2.36.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-946h-jp5c-8fvh is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

### 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 `searchable_fields` defaults to every property of the entity and the autocomplete endpoint is public by default (`BaseEntityAutocompleteType` ships with `security => false`

O3 Security · Impact-Aware SCA

Is GHSA-946h-jp5c-8fvh in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

symfony/ux-autocomplete: Information exposure via unescaped LIKE wildcards in EntitySearchUtilGHSA-946h-jp5c-8fvh

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

Real-World Exposure

Description

Description

Resolution

Credits

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-946h-jp5c-8fvh in your dependencies?