{"items":[{"id":"NVI-00006673","kind":"vulnerability","title":"Laravel Hijacked authentication cookies vulnerability","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-p62r-7637-3wwc"],"plain_summary":"OSV carries this publisher advisory for laravel/framework. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 4.1.26 for laravel/framework. Confirm the publisher’s latest guidance.","source_ids":["sr-be2bb36cdc89e501170ab864916a1b1f"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-be2bb36cdc89e501170ab864916a1b1f","url":"https://github.com/advisories/GHSA-p62r-7637-3wwc","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-p62r-7637-3wwc","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.986Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-be2bb36cdc89e501170ab864916a1b1f"],"technology":"laravel/framework","known_exclusions":[],"conditions_summary":"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.\n\nThis 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.","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0; fixed 4.1.26"]}],"null_published_at":"2026-10-31T22:13:10.068Z","source_updated_at":"2024-11-29T05:26:31.327Z","source_disclosed_at":"2024-05-15T22:06:42.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:42:30.986Z"}],"next_cursor":null,"snapshot_revision":"42594"}