# CVE-2026-114508: Laravel relationship inclusion can trigger unauthorized data destruction


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 21 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-5wcm-3v2w-8362

## What is CVE-2026-114508?

CVE-2026-114508 is a medium-severity vulnerability in laravel framework, published on 21 Oct 2026. 

### Official description

Laravel is a web application framework. From 12.45.0 until 12.68.0 and 13.27.0, crafted relationship inclusion on a read-only endpoint can trigger a destructive database operation on a related table instead of retrieving data. A user with read access but no write permission can empty related-table data, causing irreversible data loss, denial of service, and loss of data integrity. This issue is fixed in versions 12.68.0 and 13.27.0.

Weakness: CWE-470 (Use of Externally-Controlled Input to Select Classes or Code)

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

4 open source packages ship an affected version, including laravel/framework.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `laravel/framework` | Packagist | From 12.45.0 | 12.68.0 |
| `laravel/framework` | Packagist | From 12.45.0 | 12.68.0 |
| `laravel/framework` | Packagist | From 13.0.0 | 13.27.0 |
| `laravel/framework` | Packagist | From 13.0.0 | 13.27.0 |

## How do I fix CVE-2026-114508?

Upgrade laravel/framework to a fixed version for your release line: 12.68.0 or 13.27.0.

## Is CVE-2026-114508 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114508 is a medium-severity vulnerability in laravel framework, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114508 in the wild and no public exploit code.

Affected packages and fixed versions:
- laravel/framework (Packagist): affected from 12.45.0; fixed in 12.68.0
- laravel/framework (Packagist): affected from 12.45.0; fixed in 12.68.0
- laravel/framework (Packagist): affected from 13.0.0; fixed in 13.27.0
- laravel/framework (Packagist): affected from 13.0.0; fixed in 13.27.0

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-114508/ (Markdown: https://insights.sbomify.com/CVE-2026-114508/index.md)
```

## Sources

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

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