CVE-2020-5255: Prevent cache poisoning via a Response Content-Type header in Symfony

low Affects symfony/http-foundation, symfony/symfony. Feed 2026.10.29.4, updated 2026-10-29; published ; advisory modified .

Prevent cache poisoning via a Response Content-Type header in Symfony

Package
symfony/http-foundation Composer
Affected versions
>=4.4.0 and <4.4.7 or >=5.0.0 and <5.0.7
Fixed in
4.4.7, 5.0.7
Severity
low  CVSS 2.6
Exploitation
not on CISA KEV · EPSS 1% (70.3th percentile)
Published
2020-03-30
Source
osv.dev

References

Prevent cache poisoning via a Response Content-Type header in Symfony

Package
symfony/symfony Composer
Affected versions
>=4.4.0 and <4.4.7 or >=5.0.0 and <5.0.7
Fixed in
4.4.7, 5.0.7
Severity
low  CVSS 2.6
Exploitation
not on CISA KEV · EPSS 1% (70.3th percentile)
Published
2020-03-30
Source
osv.dev

References

CWE-435
NVD recordsymfony/http-foundation advisoriessymfony/symfony advisories

Am I affected?

Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# PHP projects (recommended)
composer require --dev phpwarden/phpwarden
# then
vendor/bin/phpwarden deps composer.lock

# or, without Composer
pipx install phpwarden   &&   phpwarden deps composer.lock

Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command

Install docs   How findings are ranked

Related advisories