# 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.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-r33w-fg8j-9c94

## 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 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2026-61701?

2 open source packages ship an affected version, including cesargb/laravel-magiclink.


| Package | Ecosystem | 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.

## Is CVE-2026-61701 being exploited?

There is no known exploitation of CVE-2026-61701 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-61701 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-61701 in the wild and no public exploit code.

Affected packages and fixed versions:
- cesargb/laravel-magiclink (Packagist): affected from 2.0.0; fixed in 2.25.1
- cesargb/laravel-magiclink (Packagist): affected from 2.0.0; fixed in 2.25.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-61701/ (Markdown: https://insights.sbomify.com/CVE-2026-61701/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-61701
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-61701
- OSV: https://osv.dev/vulnerability/CVE-2026-61701

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-61701/
Summaries are generated and may contain mistakes; the official description above is the record.