How severe is GHSA-2867-6rrm-38gr?

No CVSS score has been assigned to GHSA-2867-6rrm-38gr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2867-6rrm-38gr?

GHSA-2867-6rrm-38gr affects the following packages: illuminate/cookie (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-2867-6rrm-38gr?

Update illuminate/cookie to 5.6.30 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2867-6rrm-38gr is resolved across your whole dependency graph.

How do I detect GHSA-2867-6rrm-38gr in my Packagist dependencies?

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

How do I mitigate GHSA-2867-6rrm-38gr if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-2867-6rrm-38gr?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2867-6rrm-38gr can be triaged on real exposure rather than presence alone.

Is GHSA-2867-6rrm-38gr actively exploited in the wild?

No public exploit code has been indexed for GHSA-2867-6rrm-38gr 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.

When was GHSA-2867-6rrm-38gr published, and has it been updated?

GHSA-2867-6rrm-38gr was published on May 15, 2024 and was last updated on November 29, 2024. 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

GHSA-2867-6rrm-38gr — illuminate/cookie

GHSA-2867-6rrm-38gr is a security vulnerability in illuminate/cookie. A fix is available for illuminate/cookie — see the affected versions and patch details below.

Laravel Cookie serialization vulnerability

Published

May 15, 2024

Updated

Nov 29, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 29, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘illuminate/cookie

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

Laravel 5.6.30 is a security release of Laravel and is recommended as an immediate upgrade for all users. Laravel 5.6.30 also contains a breaking change to cookie encryption and serialization logic. Refer to laravel advisory for more details and read the notes carefully when upgrading your application.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`illuminate/cookie`	≥ 5.5.0&&< 5.6.30	5.6.30`composer require illuminate/cookie:^5.6.30`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for illuminate/cookie, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update illuminate/cookie to 5.6.30 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2867-6rrm-38gr is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2867-6rrm-38gr can be triaged on real exposure rather than presence alone.

Tailored to GHSA-2867-6rrm-38gr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Laravel 5.6.30 is a security release of Laravel and is recommended as an immediate upgrade for all users. Laravel 5.6.30 also contains a breaking change to cookie encryption and serialization logic. Refer to [laravel advisory](https://laravel.com/docs/5.6/upgrade#upgrade-5.6.30) for more details and read the notes carefully when upgrading your application.

O3 Security · Impact-Aware SCA

Is GHSA-2867-6rrm-38gr in your dependencies?

O3 Security finds GHSA-2867-6rrm-38gr across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works