CVE-2026-61701 Laravel MagicLink: Insecure Deserialization of MagicLink Actions Leads to Remote Code Execution
Attackers with database write access can trigger remote code execution via insecure deserialization of MagicLink action objects in the Laravel MagicLink library.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-61701?
CVE-2026-61701 is a high-severity unsafe deserialization vulnerability in cesargb laravel-magiclink, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Weakness: CWE-502
Which versions are affected by CVE-2026-61701?
2 open source packages ship an affected version, including cesargb/laravel-magiclink.
| Package | Affected | Fixed in |
|---|---|---|
cesargb/laravel-magiclink Packagist | From 2.0.0 | 2.25.1 |
cesargb/laravel-magiclink Packagist | From 2.0.0 | 2.25.1 |
How do I fix CVE-2026-61701?
Upgrade cesargb/laravel-magiclink to 2.25.1 or later.
Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.
Is CVE-2026-61701 being exploited?
There is no known exploitation of CVE-2026-61701 in the wild and no public exploit code.
Sources
Also known as GHSA-r33w-fg8j-9c94.