CVE-2026-114508: Laravel relationship inclusion can trigger unauthorized data destruction
laravel/framework 12.45.0 to 12.67.x and 13.0.0 to 13.26.x can let a request to a read-only JSON:API resource endpoint trigger a destructive database operation on a related table, such as emptying it. No write permission is needed. Upgrade to 12.68.0 or 13.27.0.
Published Oct 23, 2026 · Analysis Nov 2, 2026
What an attacker can do
The advisory describes a flaw in how relationship inclusion is processed on certain read endpoints. A crafted request to a read endpoint can cause a destructive operation on a related table instead of just fetching data. The CWE is unsafe reflection: an externally controlled value selects what code runs.
The fix commit shows where. It changes the JSON:API resource code in ResolvesJsonApiElements.php. Before the fix, nested names in the include query parameter were passed on to relationship loading without being checked against the resource's real relationships. The new tests request include=comments.truncate and include=posts.comments.truncate, where truncate is not a relationship. After the fix those segments are ignored. The advisory does not give an exploit recipe, so treat the truncate test as a hint, not a confirmed payload.
The attacker needs network access to an endpoint that returns Laravel JSON:API resources and accepts include. The CVSS vector says no privileges and no user interaction. Per the advisory, the result is irreversible data loss and denial of service, with low integrity and availability impact. Data is not disclosed.
Who is affected
laravel/framework >= 12.45.0, < 12.68.0 and >= 13.0.0, < 13.27.0. The changed code is in the JSON:API resource support, so applications that do not return JSON:API resources are not shown to be exposed by the sources. Earlier 12.x versions are outside the listed range. Check your installed version:
composer show laravel/frameworkThen search your code for JSON:API resource classes and routes that serve them.
laravel/framework
- Ecosystem
- Composer (PHP)
- Affected
- >= 12.45.0, < 12.68.0
- Fixed in
- 12.68.0
- Check
composer show laravel/framework
laravel/framework
- Ecosystem
- Composer (PHP)
- Affected
- >= 13.0.0, < 13.27.0
- Fixed in
- 13.27.0
- Check
composer show laravel/framework
How to fix it
Upgrade to 12.68.0 on the 12.x line, or 13.27.0 on the 13.x line:
composer update laravel/frameworkIf your composer.json constraint blocks it, raise the minimum to ^12.68 or ^13.27. The fix (PRs 61322 and 61323) makes JSON:API resource loading use only the relationship paths that match real resource relationships, and ignore other nested include segments. The sources give no workaround. Keep current database backups until you have patched.
How to tell if you were hit
Check web and application logs for requests to JSON:API endpoints with unusual include values, especially nested segments that are not relationship names, such as include=comments.truncate. Look for related tables that are suddenly empty, and for matching DELETE or TRUNCATE statements in the database query log or audit log. Compare against a recent backup to size any loss. Requests came from read-only users or anonymous clients, so check GET traffic, not only write routes.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
A vulnerability in how relationship inclusion is processed on certain read endpoints. Under specific conditions, a request to a read-only endpoint can be crafted to trigger a destructive database operation on a related table, rather than simply retrieving data.
Impact
A user with only read access could cause irreversible data loss (e.g., a related table being emptied), without needing any write permissions. This could result in denial of service and loss of data integrity for affected applications.
Credited to KIKOmanasijev.
Questions
- Does the attacker need write permission in my Laravel app?
No. The advisory says a user with only read access can trigger the destructive operation. The CVSS vector lists no privileges required and no user interaction.
- Which Laravel versions are fixed for CVE-2026-114508?
12.68.0 on the 12.x line and 13.27.0 on the 13.x line. Vulnerable ranges are 12.45.0 up to 12.68.0 and 13.0.0 up to 13.27.0.
- Is CVE-2026-114508 exploited in the wild?
No source reports exploitation, and it is not in CISA's KEV catalog.
References
Read for this analysis:
- https://github.com/laravel/framework/security/advisories/GHSA-5wcm-3v2w-8362
- https://github.com/laravel/framework/commit/50a7970efe9f9990b6ec4f1e949de2abaaf4263e
- https://github.com/laravel/framework/pull/61322
- https://nvd.nist.gov/vuln/detail/CVE-2026-114508
- https://github.com/laravel/framework/pull/61323
- https://github.com/laravel/framework/commit/b89f2944995d555bfda76dced1ef6c6b04ef17d8
- https://github.com/laravel/framework/releases/tag/v12.68.0
- https://github.com/laravel/framework/releases/tag/v13.27.0
- https://github.com/advisories/GHSA-5wcm-3v2w-8362
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-128083
Laravel: Task Output Injection - Concurrency Process
low2.3Nov 13, 2026CVE-2026-114509
Laravel TokenGuard authentication bypass through non-string API credentials
critical9.2Oct 23, 2026CVE-2026-102279
Laravel: XSS in Debug Page Information
low3.1Sep 29, 2026GHSA-5vg9-5847-vvmq
Laravel Framework: CRLF injection in default email rule
high8.9Jun 17, 2026GHSA-crmm-hgp2-wgrp
Laravel Framework: Temporary Signed URL Path Confusion
medium4.2Jun 17, 2026CVE-2024-13918
Laravel framework susceptible to reflected cross-site scripting
medium4.7Mar 10, 2025
