Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-22814: CWE-915: Improperly Controlled Modification of Dynamically-Determined Object Attributes in adonisjs lucid

0
High
VulnerabilityCVE-2026-22814cvecve-2026-22814cwe-915
Published: Tue Jan 13 2026 (01/13/2026, 19:42:14 UTC)
Source: CVE Database V5
Vendor/Project: adonisjs
Product: lucid

Description

CVE-2026-22814 is a high-severity mass assignment vulnerability in the AdonisJS Lucid ORM affecting versions prior to 21. 8. 2 and certain pre-release 22. x versions. It allows remote attackers who can influence input data to overwrite internal ORM state, potentially leading to unauthorized modification of database records and logic bypasses. No user interaction or authentication is required, and exploitation can be performed remotely over the network. The vulnerability has been patched in versions 21. 8. 2 and 22. 0.

AI-Powered Analysis

AILast updated: 01/21/2026, 02:32:26 UTC

Technical Analysis

CVE-2026-22814 is a vulnerability classified under CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes) found in the @adonisjs/lucid SQL ORM, which is built on top of Knex for the AdonisJS framework. The flaw exists in versions prior to 21.8.2 and certain pre-release 22.x versions before 22.0.0-next.6. It is a mass assignment vulnerability, meaning that an attacker who can influence the data passed into Lucid model assignments can manipulate internal ORM state. This manipulation allows unauthorized overwriting of model attributes, potentially leading to logic bypasses and unauthorized modification of database records within the affected tables or models. The vulnerability is remotely exploitable without requiring authentication or user interaction, increasing its risk profile. The CVSS 4.0 score is 8.2 (high), reflecting the network attack vector, low complexity, no privileges required, no user interaction, and high impact on integrity. The vulnerability was publicly disclosed on January 13, 2026, and patches were released in versions 21.8.2 and 22.0.0-next.6. No known exploits have been reported in the wild yet. The root cause is insufficient control over which attributes can be mass-assigned in the ORM, allowing attackers to overwrite sensitive or internal state attributes that should be protected. This can lead to unauthorized data changes and potentially compromise application logic relying on ORM state integrity.

Potential Impact

For European organizations, this vulnerability poses a significant risk to the confidentiality and integrity of data managed through applications using the affected versions of AdonisJS Lucid. Unauthorized modification of database records can lead to data corruption, privilege escalation within the application, and bypass of business logic controls. This is particularly critical for sectors handling sensitive or regulated data such as finance, healthcare, and government services. The remote and unauthenticated nature of the exploit increases the attack surface, especially for public-facing web applications. Organizations relying on Node.js and AdonisJS frameworks for backend services may experience service disruption or data integrity issues if exploited. The lack of known exploits in the wild currently provides a window for remediation, but the ease of exploitation and high impact necessitate immediate action to prevent potential attacks. The vulnerability could also undermine trust in affected applications and lead to regulatory compliance issues under GDPR if personal data integrity is compromised.

Mitigation Recommendations

1. Immediately upgrade all instances of @adonisjs/lucid to version 21.8.2 or later, or to 22.0.0-next.6 or later for pre-release users. 2. Review and harden model attribute assignments by explicitly defining allowed fields for mass assignment, using ORM features such as 'fillable' or 'guarded' properties to restrict which attributes can be set via user input. 3. Implement input validation and sanitization to prevent injection of malicious attribute data. 4. Conduct thorough code audits focusing on areas where model data is assigned from external sources, ensuring no sensitive internal attributes are exposed. 5. Monitor application logs for unusual modification patterns or unauthorized changes to database records. 6. Employ runtime application self-protection (RASP) or web application firewalls (WAF) with custom rules to detect and block suspicious ORM-related requests. 7. Educate development teams on secure ORM usage patterns to prevent similar vulnerabilities in future development. 8. Establish incident response plans to quickly address any exploitation attempts.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-01-09T22:50:10.288Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6966a38da60475309fabea81

Added to database: 1/13/2026, 7:57:01 PM

Last enriched: 1/21/2026, 2:32:26 AM

Last updated: 2/7/2026, 12:39:16 PM

Views: 49

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats