2018-08-08-1: Cookie serialization vulnerability

unknown Affects illuminate/cookie, laravel/framework. Feed 2026.10.29.4, updated 2026-10-29.

Cookie serialization vulnerability

Package
illuminate/cookie Composer
Affected versions
>=4.0.0 and <=4.0.11 or >=4.1.0 and <=4.1.31 or >=4.2.0 and <=4.2.22 or >=5.0.0 and <=5.0.35 or >=5.1.0 and <=5.1.46 or >=5.2.0 and <=5.2.45 or >=5.3.0 and <=5.3.31 or >=5.4.0 and <=5.4.36 or >=5.5.0 and <5.5.42 or >=5.6.0 and <5.6.30
Fixed in
5.5.42, 5.6.30
Severity
unknown
Exploitation
not on CISA KEV
Source
friendsofphp

References

Cookie serialization vulnerability

Package
laravel/framework Composer
Affected versions
>=4.0.0 and <=4.0.11 or >=4.1.0 and <=4.1.31 or >=4.2.0 and <=4.2.22 or >=5.0.0 and <=5.0.35 or >=5.1.0 and <=5.1.46 or >=5.2.0 and <=5.2.45 or >=5.3.0 and <=5.3.31 or >=5.4.0 and <=5.4.36 or >=5.5.0 and <5.5.42 or >=5.6.0 and <5.6.30
Fixed in
5.5.42, 5.6.30
Severity
unknown
Exploitation
not on CISA KEV
Source
friendsofphp

References

NVD recordilluminate/cookie advisorieslaravel/framework 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