What is GHSA-2FFV-R4R9-R8XR?

GHSA-2FFV-R4R9-R8XR is a critical-severity code injection vulnerability in illuminate/cookie (composer), affecting versions >= 4.1.0, < 6.18.31. It is fixed in 6.18.31, 7.22.4. Untrusted input is evaluated as executable code within the application's runtime environment.

Which versions of illuminate/cookie are affected by GHSA-2FFV-R4R9-R8XR?

illuminate/cookie (composer) versions >= 4.1.0, < 6.18.31 is affected.

Is there a fix for GHSA-2FFV-R4R9-R8XR?

Yes. GHSA-2FFV-R4R9-R8XR is fixed in 6.18.31, 7.22.4. Upgrade to this version or later.

Is GHSA-2FFV-R4R9-R8XR exploitable, and should I be worried?

Whether GHSA-2FFV-R4R9-R8XR is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-2FFV-R4R9-R8XR is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-2FFV-R4R9-R8XR in illuminate/cookie

Q: Which versions of illuminate/cookie are affected by GHSA-2FFV-R4R9-R8XR?

illuminate/cookie (composer) versions >= 4.1.0, < 6.18.31 is affected.

Q: Is there a fix for GHSA-2FFV-R4R9-R8XR?

Yes. GHSA-2FFV-R4R9-R8XR is fixed in 6.18.31, 7.22.4. Upgrade to this version or later.

Q: Is GHSA-2FFV-R4R9-R8XR exploitable, and should I be worried?

Whether GHSA-2FFV-R4R9-R8XR is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-2FFV-R4R9-R8XR is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-2FFV-R4R9-R8XR?

Upgrade: illuminate/cookie to 6.18.31 or later, illuminate/cookie to 7.22.4 or later.

Summary

Laravel RCE vulnerability in "cookie" session driver

Application's using the "cookie" session driver were the primary applications affected by this vulnerability. Since we have not yet released a security release for the Laravel 5.5 version of the framework, we recommend that all applications running Laravel 5.5 and earlier do not use the "cookie" session driver in their production deployments.

Regarding the vulnerability, applications using the "cookie" session driver that were also exposing an encryption oracle via their application were vulnerable to remote code execution. An encryption oracle is a mechanism where arbitrary user input is encrypted and the encrypted string is later displayed or exposed to the user. This combination of scenarios lets the user generate valid Laravel signed encryption strings for any plain-text string, thus allowing them to craft Laravel session payloads when an application is using the "cookie" driver.

This fix prefixes cookie values with an HMAC hash of the cookie's name before encryption and then verifies a matching hash on decryption, making it impossible to craft a valid cookie payload even if an encryption oracle is exposed via the application.

Impact

Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.

Affected versions

illuminate/cookie (>= 4.1.0, < 6.18.31) illuminate/cookie (>= 7.0.0, < 7.22.4)

Security releases

illuminate/cookie → 6.18.31 (composer) illuminate/cookie → 7.22.4 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

illuminate/cookie to 6.18.31 or later; illuminate/cookie to 7.22.4 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-2FFV-R4R9-R8XR? GHSA-2FFV-R4R9-R8XR is a critical-severity code injection vulnerability in illuminate/cookie (composer), affecting versions >= 4.1.0, < 6.18.31. It is fixed in 6.18.31, 7.22.4. Untrusted input is evaluated as executable code within the application's runtime environment.
Which versions of illuminate/cookie are affected by GHSA-2FFV-R4R9-R8XR? illuminate/cookie (composer) versions >= 4.1.0, < 6.18.31 is affected.
Is there a fix for GHSA-2FFV-R4R9-R8XR? Yes. GHSA-2FFV-R4R9-R8XR is fixed in 6.18.31, 7.22.4. Upgrade to this version or later.
Is GHSA-2FFV-R4R9-R8XR exploitable, and should I be worried? Whether GHSA-2FFV-R4R9-R8XR is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-2FFV-R4R9-R8XR is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-2FFV-R4R9-R8XR?
- Upgrade illuminate/cookie to 6.18.31 or later
- Upgrade illuminate/cookie to 7.22.4 or later

Other vulnerabilities in illuminate/cookie

CVE-IDSeverityPackage summary

GHSA-2867-6RRM-38GRHighilluminate/cookie: Laravel Cookie serialization vulnerability