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 record modifications and logic bypasses. Exploitation requires no authentication or user interaction and can be performed remotely over the network. The vulnerability impacts data integrity and application logic but does not affect confidentiality or availability directly. It has been patched in versions 21. 8. 2 and 22.

AI-Powered Analysis

AILast updated: 01/13/2026, 20:10:56 UTC

Technical Analysis

CVE-2026-22814 identifies a mass assignment vulnerability in the AdonisJS Lucid ORM, a SQL ORM built on top of Knex for the AdonisJS framework. The flaw arises from improperly controlled modification of dynamically-determined object attributes (CWE-915), allowing an attacker who can influence data passed into Lucid model assignments to overwrite internal ORM state. This can lead to unauthorized modifications of database records or bypassing application logic constraints. The vulnerability affects @adonisjs/lucid versions prior to 21.8.2 and pre-release versions 22.0.0-next.0 through 22.0.0-next.5. Exploitation requires no privileges or user interaction and can be conducted remotely, making it highly accessible to attackers. The CVSS 4.0 score of 8.2 reflects the vulnerability's high impact on integrity and the ease of exploitation. Although no public exploits are known, the potential for unauthorized data manipulation within affected applications is significant. The issue was addressed by patches in versions 21.8.2 and 22.0.0-next.6, which enforce stricter controls on attribute assignment to prevent mass assignment attacks.

Potential Impact

For European organizations, this vulnerability poses a substantial risk to the integrity of data managed by web applications using the affected versions of AdonisJS Lucid. Attackers could manipulate database records, potentially altering critical business data, bypassing authorization logic, or corrupting application workflows. This could lead to financial losses, regulatory non-compliance (especially under GDPR if personal data integrity is compromised), and reputational damage. Since the vulnerability does not require authentication, it increases the attack surface, particularly for internet-facing applications. The impact is especially critical for sectors relying heavily on Node.js frameworks for backend services, including fintech, e-commerce, and public sector digital services. The absence of known exploits in the wild provides a window for proactive mitigation but should not reduce urgency.

Mitigation Recommendations

European organizations should immediately audit their use of AdonisJS Lucid ORM to identify affected versions. The primary mitigation is to upgrade to version 21.8.2 or later, or 22.0.0-next.6 or later, where the vulnerability is patched. Additionally, developers should implement strict input validation and whitelist attributes allowed for mass assignment to reduce exposure. Employing runtime application self-protection (RASP) or web application firewalls (WAF) with rules targeting unusual ORM attribute modifications can provide temporary defense. Conduct thorough code reviews focusing on model assignment logic and ensure that sensitive attributes are never directly assignable from user input. Monitoring application logs for suspicious modification patterns can help detect exploitation attempts. Finally, integrate security testing into the CI/CD pipeline to catch similar issues early in development.

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/13/2026, 8:10:56 PM

Last updated: 1/13/2026, 9:14:46 PM

Views: 5

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