All reports
High

Symfony collectionCascaded and collectionCascadedDeeply fields security bypass

Affected versions

Version ranges need review.

Affected versions
>= 2.1.0, < 2.1.12
Fixed version
2.1.12
Affected versions
>=2.0.0,<2.0.24|>=2.1.0,<2.1.12|>=2.2.0,<2.2.5|>=2.3.0,<2.3.3
Fixed version
Not reported
Affected versions
>= 2.3.0, < 2.3.3
Fixed version
2.3.3
Affected versions
>= 2.2.0, < 2.2.5
Fixed version
2.2.5
Affected versions
>= 2.0.0, < 2.0.24
Fixed version
2.0.24
Affected versions
>=2.0.0,<2.0.24|>=2.1.0,<2.1.12|>=2.2.0,<2.2.5|>=2.3.0,<2.3.3
Fixed version
Not reported
Affected versions
>= 2.1.0, < 2.1.12
Fixed version
2.1.12
Affected versions
>= 2.2.0, < 2.2.5
Fixed version
2.2.5
Affected versions
>= 2.3.0, < 2.3.3
Fixed version
2.3.3
Affected versions
>= 2.0.0, < 2.0.24
Fixed version
2.0.24

Exploitation

CVE-2013-4751

Probability of exploitation in the next 30 days: 1.45%

FIRST EPSS · 2026-11-20

Description

When using the Validator component, if Symfony\\Component\\Validator\\Mapping\\Cache\\ApcCache is enabled (or any other cache implementing Symfony\\Component\\Validator\\Mapping\\Cache\\CacheInterface), some information is lost during serialization (the collectionCascaded and the collectionCascadedDeeply fields).

As a consequence, arrays or traversable objects stored in fields using the @Valid constraint are not traversed by the validator as soon as the validator configuration is loaded from the cache.

Links