Symfony Vulnerable to SQL Injection in PdoAdapter::doClear() via Unsanitized $prefix
Published 27 May 2026 · Updated 10 Sept 2026
Affected packages
- Affected
- <5.4.52
- Fixed in
- 5.4.52
composer require symfony/cache:^5.4.52- Affected
- >=6.0.0 <6.4.40
- Fixed in
- 6.4.40
composer require symfony/cache:^6.4.40- Affected
- >=7.0.0 <7.4.12
- Fixed in
- 7.4.12
composer require symfony/cache:^7.4.12- Affected
- >=8.0.0 <8.0.12
- Fixed in
- 8.0.12
composer require symfony/cache:^8.0.12- Affected
- <5.4.52
- Fixed in
- 5.4.52
composer require symfony/symfony:^5.4.52- Affected
- >=6.0.0 <6.4.40
- Fixed in
- 6.4.40
composer require symfony/symfony:^6.4.40- Affected
- >=7.0.0 <7.4.12
- Fixed in
- 7.4.12
composer require symfony/symfony:^7.4.12- Affected
- >=8.0.0 <8.0.12
- Fixed in
- 8.0.12
composer require symfony/symfony:^8.0.12Details
Description
Symfony\Component\Cache\Adapter\PdoAdapter is the PDO-backed cache adapter. Its clear($prefix) method (inherited from AbstractAdapterTrait) is documented to delete cache items whose key starts with $prefix.
In the non-versioning code path, the caller-supplied $prefix is concatenated into $namespace = $this->namespace.$prefix and passed to PdoAdapter::doClear(), which builds:
DELETE FROM <table> WHERE <id_col> LIKE '<namespace>%'
The value is interpolated directly into the SQL text and executed with PDO::exec(): $namespace is not bound. A caller able to influence $prefix can break out of the literal and inject SQL, expanding deletion scope from the intended prefix to arbitrary rows, or otherwise reshape query semantics.
Most applications don't expose clear($prefix) to untrusted input directly, but the contract of the method is to safely accept any prefix string, so the lack of escaping is a defect of the adapter itself.
Resolution
AbstractAdapterTrait::clear() now rejects any $prefix containing characters outside [-+.A-Za-z0-9]: when an invalid prefix is supplied, the method logs a warning and returns false instead of reaching the SQL layer. This blocks quotes, %, null bytes and other characters that would let an attacker break out of the LIKE literal.
The patch for this issue is available here for branch 5.4.
Credits
Symfony would like to thank secsys_codex for reporting the issue and Nicolas Grekas for fixing it.
Is GHSA-6qh9-h6wf-jgqc in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected symfony/cache, and gives you the command that fixes it.
References
- Linkgithub.com/symfony/symfony/security/advisories/GHSA-6qh9-h6wf-jgqc
- Linkgithub.com/symfony/symfony/commit/ec50b799d79ebe24561f29351c1efcb6da95c9b
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/symfony/cache/CVE-2026-45073.yaml
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/symfony/symfony/CVE-2026-45073.yaml
- Packagegithub.com/symfony/symfony
- Linksymfony.com/cve-2026-45073
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.