Laravel: Relationship Includes on Read Endpoints Can Destroy Data

Published as "Laravel relationship inclusion can trigger unauthorized data destruction"

medium Laravel Laravel framework · Last reviewed Oct 31, 2026

CVE: CVE-2026-114508
GHSA: GHSA-5wcm-3v2w-8362
Packagist: PKSA-4hy6-m98j-dz9f
Reported: Oct 23, 2026

Lets a user with only read access trigger a destructive query, such as emptying a related table, through relationship includes in some Laravel apps.

Affected and fixed versions

In laravel/framework. Find the row for the version you run, and update to the release next to it.

If you run	Update to	Support
13.0.0 – 13.26.x	13.27.0	Supported
12.45.0 – 12.67.x	12.68.0	Supported

Upgrade

Run the line for the branch you are on.

composer require laravel/framework:^13.27.0
composer require laravel/framework:^12.68.0

What this means

A user with only read access can make a read-only endpoint run a destructive database operation on a related table, for example emptying it. They don't need any write permission, and the data loss can't be undone.

Who is affected

Apps on laravel/framework from 12.45.0 up to (not including) 12.68.0, or 13.x before 13.27.0, with endpoints that let clients choose which related records to include in a response. The Laravel advisory says it only happens under specific conditions and doesn't list them.

The fix changes how Laravel's JSON:API resources (JsonApiResource) load the relationships a request asks for. If your app returns those resources, it's the code to check. Releases before 12.45.0 aren't affected.

What to do

Update laravel/framework to 13.27.0 if you're on 13.x, or to 12.68.0 if you're on 12.x.

Reported by KIKOmanasijev.

Check your app with an agent

Paste this into a coding agent that can read your project, such as Claude Code, Codex or Amp. It checks your composer.lock against the versions above and tells you what to update, without changing anything.

Check whether the PHP project you have access to is affected by this security advisory, and tell me what to update. Do a read-only check: don't edit files, don't run composer update or composer require, and don't try to reproduce the flaw.

Advisory: Laravel: Relationship Includes on Read Endpoints Can Destroy Data (CVE-2026-114508, GHSA-5wcm-3v2w-8362)
Details: https://phpnews.net/security/laravel/ghsa-5wcm-3v2w-8362

Affected versions, as Composer constraints:
- laravel/framework: >=13.0.0,<13.27.0|>=12.45.0,<12.68.0

Fixed releases on branches that still get security fixes:
- 13.0.0 – 13.26.x: update to 13.27.0
- 12.45.0 – 12.67.x: update to 12.68.0

1. Find every composer.lock in the project outside vendor/ (a monorepo can have one per app) and read the installed version of each package above. Packages installed as dependencies of other packages count too.
2. Compare each installed version with its constraint: "|" separates alternative ranges, and "," means both bounds apply.
3. For each affected install, read "What this means" at https://phpnews.net/security/laravel/ghsa-5wcm-3v2w-8362 and check whether the project meets the conditions it describes (a feature in use, a config value, a driver). Say which conditions you could check and which you couldn't.
4. Report a table: lock file | package | installed version | affected (yes, no or unknown) | conditions met (yes, no or unknown) | update to | evidence. For each affected package, give the command that would fix it, without running it: composer update <package> --with-dependencies when it is only installed as a dependency of another package, or composer require with the fixed version when composer.json requires it directly. If the installed version is on a branch with no fixed release listed, say it needs a move to a newer branch.

Sources

← All Laravel advisories