Skip to main content
VulnerabilityPublished

CVE-2026-61701: cesargb laravel-magiclink · Deserialization of Untrusted Data

Affects cesargb laravel-magiclinkSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 2.25.1 soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.25.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade laravel-magiclink and cesargb/laravel-magiclink to 2.25.1.

Affected software

ProductAffectedFixed in
cesargblaravel-magiclinkAffected
  • >=2.0.0 <2.25.1
Fixed in
  • 2.25.1
GitHubcesargb/laravel-magiclinkpkg:github/cesargb/laravel-magiclinkOther threatsAffected
  • >=2.0.0 <2.25.1
Fixed in
  • 2.25.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade laravel-magiclink to version 2.25.1 or later, where this vulnerability is fixed. Until then, ensure that database write access is tightly controlled and monitor for any unauthorized modifications to the magic_links.action column. Patch status is confirmed fixed in 2.25.1.

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.

References

Community reviews

Loading reviews…