CVE-2026-61701

published 14 Sep 2026 · updated 14 Sep 2026

Laravel MagicLink: Insecure Deserialization of MagicLink Actions Leads to Remote Code Execution

8.8HighCVSS 8.8EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. No fixed version is recorded.

Laravel MagicLink creates links for authentication without a password or for accessing private content. From 2.0.0 until 2.25.1, MagicLink stores serialized action objects in the magic_links.action database column and deserializes them through src/MagicLink.php and src/Actions/ResponseAction.php without sufficient integrity protection, while an unsafe legacy unserialize() fallback remains reachable. An attacker who can manipulate database records, such as through a separate SQL injection or compromised administrative access, can insert a malicious serialized object graph containing executable closure behavior; visiting the associated magic link then deserializes the record and can execute arbitrary code in the application process. The affected path is restricted to manipulated action records and does not independently provide database-write access. This issue is fixed in version 2.25.1.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
cesargb>=2.0.0 <2.25.1

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-61701 severity on Zeptric[![CVE-2026-61701](https://zeptric.io/badge/cve/CVE-2026-61701.svg)](https://zeptric.io/cve/CVE-2026-61701)