How severe is GHSA-q4xf-7fw5-4x8v?

No CVSS score has been assigned to GHSA-q4xf-7fw5-4x8v yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-q4xf-7fw5-4x8v?

GHSA-q4xf-7fw5-4x8v affects the following packages: illuminate/auth (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-q4xf-7fw5-4x8v?

Update illuminate/auth to 4.1.26 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q4xf-7fw5-4x8v is resolved across your whole dependency graph.

How do I detect GHSA-q4xf-7fw5-4x8v in my Packagist dependencies?

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

How do I mitigate GHSA-q4xf-7fw5-4x8v 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-q4xf-7fw5-4x8v?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-q4xf-7fw5-4x8v can be triaged on real exposure rather than presence alone.

Is GHSA-q4xf-7fw5-4x8v actively exploited in the wild?

No public exploit code has been indexed for GHSA-q4xf-7fw5-4x8v 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-q4xf-7fw5-4x8v published, and has it been updated?

GHSA-q4xf-7fw5-4x8v 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-q4xf-7fw5-4x8v — illuminate/auth

GHSA-q4xf-7fw5-4x8v is a security vulnerability in illuminate/auth. A fix is available for illuminate/auth — see the affected versions and patch details below.

Laravel Hijacked authentication cookies 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/auth

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

This change requires the addition of a new remember_token column to your users (or equivalent) database table. After this change, a fresh token will be assigned to the user each time they login to your application. The token will also be refreshed when the user logs out of the application. The implications of this change are: if a "remember me" cookie is hijacked, simply logging out of the application will invalidate the cookie.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`illuminate/auth`	≥ 4.0.0&&< 4.1.26	4.1.26`composer require illuminate/auth:^4.1.26`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for illuminate/auth, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update illuminate/auth to 4.1.26 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q4xf-7fw5-4x8v 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-q4xf-7fw5-4x8v can be triaged on real exposure rather than presence alone.

Tailored to GHSA-q4xf-7fw5-4x8v. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Laravel 4.1.26 introduces security improvements for "remember me" cookies. Before this update, if a remember cookie was hijacked by another malicious user, the cookie would remain valid for a long period of time, even after the true owner of the account reset their password, logged out, etc. This change requires the addition of a new remember_token column to your users (or equivalent) database table. After this change, a fresh token will be assigned to the user each time they login to your application. The token will also be refreshed when the user logs out of the application. The implication

O3 Security · Impact-Aware SCA

Is GHSA-q4xf-7fw5-4x8v in your dependencies?

O3 Security finds GHSA-q4xf-7fw5-4x8v 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