Laravel framework relationship inclusion can cause unauthorized related-table data destruction

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-114508?

CVE-2026-114508 is a vulnerability classified as Use of Externally-Controlled Input to Select Classes or Code, affecting framework (affected versions: >= 12.45.0, < 12.68.0 and >= 13.0.0, < 13.27.0). This vulnerability is rated Medium, with a CVSS score of 6.5. Current sources do not report this vulnerability as exploited.

Overview

Original source data

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.

Affected products and scope

  • laravel/framework 12.x is affected from 12.45.0 inclusive through before 12.68.0; the confirmed fix for this branch is 12.68.0.
  • laravel/framework 13.x is affected from 13.0.0 inclusive through before 13.27.0; the confirmed fix for this branch is 13.27.0.
  • The supplied evidence does not establish the status of branches or deployment forms outside these ranges. Do not infer that every other branch is unaffected.

Technical details

The flaw is in how Laravel processes relationship inclusion on certain read-only endpoints, including the JSON:API resource-resolution path. Attacker-controlled relationship inclusion in a request can cause the framework to perform a destructive database operation on a related table instead of retrieving data. The source description states that a user with read access but no write permission can trigger the behavior. The fix changes Illuminate\Http\Resources\JsonApi\Concerns\ResolvesJsonApiElements and associated JSON:API integration tests. The exact endpoint contract, inclusion syntax, database statement, and relationship conditions that determine the affected table are not established by the reviewed evidence.

Exploitability

  • Reachability: The issue is reachable through a network request to an affected read-only endpoint that supports relationship inclusion.
  • Authorization: The vulnerability description states that read access without write permission can be sufficient. The structured scoring metadata describes no privileges required, so the exact authentication boundary between the sources is not fully reconciled.
  • Complexity and interaction: The structured record describes low complexity and no user interaction.
  • Status: The supplied record marks public exploit as false, while known exploitation is not established. This does not prove that exploitation has not occurred.

Technical impact

The flaw allows a request to a read endpoint to cause a destructive database operation on a related table instead of returning data. The confirmed technical outcome is data deletion with possible integrity and availability consequences; no data disclosure is established. The vulnerability description assumes a user with read access but no write permission, while the structured scoring metadata states that no privileges are required, so the precise authentication precondition must be checked against the application's endpoint exposure. The affected blast radius depends on the relationships and tables reachable through each application's read endpoints.

Business impact

  • A read-capable user may be able to empty related-table data without write permission, according to the vulnerability description.
  • Deleted data may be unrecoverable without suitable backups or other recovery procedures.
  • Loss of related records can disrupt application workflows and undermine data integrity.
  • No data-disclosure consequence is described; the documented business exposure is concentrated in data loss, service disruption, and integrity impact.

Remediation

  1. Upgrade the 12.x branch to exactly 12.68.0, or the 13.x branch to exactly 13.27.0, according to the branch deployed. Do not substitute the fixed release from one branch for the fixed release from the other.
  2. Verify the deployed package version across the full application fleet and reconcile it with the lockfile, including workers, containers, and hosts that may run different builds.
  3. Recheck read-only endpoints that support relationship inclusion after the update and confirm that the JSON:API resource-resolution fix is present in the deployed framework.
  4. If an immediate update is not possible, consider temporarily restricting or disabling relationship inclusion on exposed read-only endpoints where the application design permits it. This is an application-level precaution, not a vendor-confirmed patch.
  5. Review related-table integrity and prepare restoration from a known-good backup if destructive activity or data loss is identified.

Detection

  1. Inventory every deployment using laravel/framework and compare the deployed package version with the affected release branches.
  2. Identify read-only endpoints that accept relationship inclusion and map the related tables they can reach.
  3. Review application and database audit logs for requests to those endpoints followed by destructive database activity or an unexpected reduction in related-table row counts.
  4. Correlate data changes with request timing and request identity. Treat this as precautionary investigation because no exact parameter, log signature, or IOC is established in the available evidence.
  5. Check the integrity of related tables and confirm that backups or other recovery mechanisms are available if data loss is found.
Sources (23)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.