PatchSiren cyber security CVE debrief
CVE-2026-114508 laravel CVE debrief
A vulnerability in Laravel's relationship inclusion processing on certain read endpoints allows a user with only read access to cause irreversible data loss without needing write permissions, potentially resulting in denial of service and loss of data integrity. This issue affects applications using Laravel framework versions between 12.45.0 and 12.68.0 or between 13.0.0 and 13.27.0. Defenders should assess exposure and apply patches to prevent data loss and service disruption. The vulnerability is confirmed in these versions, and official patches are available in versions 12.68.0 and 13.27.0.
- Vendor
- laravel
- Product
- laravel/framework
- CVSS
- MEDIUM 6.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-23
- Original CVE updated
- 2026-10-23
- Advisory published
- 2026-10-23
- Advisory updated
- 2026-10-23
Who should care
Defenders responsible for applications using Laravel framework versions between 12.45.0 and 12.68.0 or between 13.0.0 and 13.27.0 should assess exposure and apply patches to prevent data loss and service disruption.
Why it matters
Defenders should care about CVE-2026-114508 because it allows unauthorized data destruction and denial of service in Laravel applications, requiring verification of exposure and prompt patching.
- Potential data loss due to destructive database operations.
- Denial of service for affected applications.
- Loss of data integrity for affected applications.
- Need for verification of exposure and application of patches.
Technical summary
The vulnerability in Laravel's relationship inclusion processing allows a crafted request to a read-only endpoint to trigger a destructive database operation on a related table, leading to irreversible data loss. This occurs in Laravel framework versions between 12.45.0 and 12.68.0 or between 13.0.0 and 13.27.0. The vulnerability can be mitigated by applying patches in versions 12.68.0 and 13.27.0. Defenders should prioritize verifying exposure, assessing affected applications, and applying patches to prevent data loss and service disruption.
Defensive priority
Defenders should prioritize verifying exposure, assessing affected applications, and applying patches to prevent data loss and service disruption.
Recommended defensive actions
- Verify if applications using Laravel framework versions between 12.45.0 and 12.68.0 or between 13.0.0 and 13.27.0 are exposed.
- Assess the potential impact of data loss and denial of service for affected applications.
- Apply patches to upgrade to Laravel framework version 12.68.0 or 13.27.0.
- Monitor for suspicious activity that could indicate exploitation attempts.
- Review compensating controls for exposed systems while remediation is scheduled and verified.
- Check relevant monitoring, detection, and logs for exposed assets that need extra review.
- Track exceptions, retest remediated assets, and close the item only after evidence is documented.
Evidence notes
The vulnerability is confirmed in Laravel framework versions between 12.45.0 and 12.68.0 and between 13.0.0 and 13.27.0. Official patches are available in versions 12.68.0 and 13.27.0. Evidence is based on source item provided by osv_dev. The source details are limited, so defenders should verify exposure and apply patches cautiously. Additional verification steps are recommended to ensure the absence of exploitation attempts.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-114508 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-114508
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-114508 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-114508
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Laravel relationship inclusion can trigger unauthorized data destruction
Unverified legacy reference
URL: https://storage.googleapis.com/osv-vulnerabilities/Packagist/GHSA-5wcm-3v2w-8362.json
osv_dev
-
Source reference
Unverified legacy reference
URL: https://github.com/laravel/framework/security/advisories/GHSA-5wcm-3v2w-8362
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://github.com/laravel/framework/pull/61322
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://github.com/laravel/framework/pull/61323
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://github.com/laravel/framework/commit/50a7970efe9f9990b6ec4f1e949de2abaaf4263e
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://github.com/laravel/framework/commit/b89f2944995d555bfda76dced1ef6c6b04ef17d8
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://github.com/laravel/framework
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://github.com/laravel/framework/releases/tag/v12.68.0
Supplemental source
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.