Laravel up to 12.67.x/13.26.x Relationship privileges management

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Laravel up to 12.67.x/13.26.x. The affected element is an unknown function of the component Relationship. Performing a manipulation results in privileges management. This vulnerability was named CVE-2026-114508. The attack may be initiated remotely. There is no available exploit. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Laravel up to 12.67.x/13.26.x. It has been classified as problematic. This affects an unknown functionality of the component Relationship. The manipulation with an unknown input leads to a privileges management vulnerability. CWE is classifying the issue as CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. This is going to have an impact on integrity, and availability. The summary by CVE is:

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.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-114508 since 10/21/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.

Upgrading to version 12.68.0 or 13.27.0 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Laravel

Version

• 12.0
• 12.1
• 12.2
• 12.3
• 12.4
• 12.5
• 12.6
• 12.7
• 12.8
• 12.9
• 12.10
• 12.11
• 12.12
• 12.13
• 12.14
• 12.15
• 12.16
• 12.17
• 12.18
• 12.19
• 12.20
• 12.21
• 12.22
• 12.23
• 12.24
• 12.25
• 12.26
• 12.27
• 12.28
• 12.29
• 12.30
• 12.31
• 12.32
• 12.33
• 12.34
• 12.35
• 12.36
• 12.37
• 12.38
• 12.39
• 12.40
• 12.41
• 12.42
• 12.43
• 12.44
• 12.45
• 12.46
• 12.47
• 12.48
• 12.49
• 12.50
• 12.51
• 12.52
• 12.53
• 12.54
• 12.55
• 12.56
• 12.57
• 12.58
• 12.59
• 12.60
• 12.61
• 12.62
• 12.63
• 12.64
• 12.65
• 12.66
• 12.67
• 13.0
• 13.1
• 13.2
• 13.3
• 13.4
• 13.5
• 13.6
• 13.7
• 13.8
• 13.9
• 13.10
• 13.11
• 13.12
• 13.13
• 13.14
• 13.15
• 13.16
• 13.17
• 13.18
• 13.19
• 13.20
• 13.21
• 13.22
• 13.23
• 13.24
• 13.25
• 13.26

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion