CVE-2026-22814 — @adonisjs/lucid
CVE-2026-22814 is a CWE-915 vulnerability in @adonisjs/lucid. A fix is available for @adonisjs/lucid — see the affected versions and patch details below.
Mass Assignment in AdonisJS Lucid Allows Overwriting Internal ORM State
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-22814.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@adonisjs/lucidnpmDescription
Summary
Description A Mass Assignment (CWE-915) vulnerability in AdonisJS Lucid may allow a remote attacker who can influence data that is passed into Lucid model assignments to overwrite the internal ORM state. This may lead to logic bypasses and unauthorized record modification within a table or model. This affects @adonisjs/lucid through version 21.8.1 and 22.x pre-release versions prior to 22.0.0-next.6. This has been patched in @adonisjs/lucid versions 21.8.2 and 22.0.0-next.6.
Details
A vulnerability in the BaseModelImpl class of @adonisjs/lucid may allow an attacker to overwrite internal class properties (such as $isPersisted, $attributes, or $isDeleted) when passing plain objects to model assignment methods.
The library relies on a this.hasOwnProperty(key) check to validate assignment targets. However, because internal ORM state properties are initialized as instance properties, they pass this check. Consequently, if an attacker can influence specific keys (like $isPersisted) into the payload passed to merge() or $consumeAdapterResult(), they can hijack the ORM's internal logic.
The exposed internal properties include:
$attributes: The raw storage for model data.$isPersisted: Controls whethersave()performs anINSERTor anUPDATE.$original: Stores the original state of the record used to calculate changes.$isDeleted: Prevents operations on deleted models.
This issue propagates to the entire write surface of the library, including:
- Instance methods
fillandmerge. - Single record creation methods
create,createQuietly,firstOrNew, andfirstOrCreate. - Conditional updates via
updateOrCreate. - Bulk operations
createMany,createManyQuietly,fetchOrNewUpMany,fetchOrCreateMany, andupdateOrCreateMany.
Impact
Applications are vulnerable if they pass unvalidated data or validated data that retains unknown properties to the model. This occurs because internal keys exist as instance properties, causing them to pass the hasOwnProperty check and bypass Lucid's default rejection of unknown properties.
Applications utilizing strict allow lists for input validation that discard unknown properties are not affected.
For example, if a developer passes request.all(), request.except() or a schema with allowUnknownProperties to Model.create(), the ORM's internal logic can be hijacked. Because the Model.create() > save() decision is based on $isPersisted, and merge() can assign to the own-property $isPersisted, an attacker who can inject "$isPersisted": true into the payload can force save() to take the UPDATE branch rather than the INSERT branch, while setting $attributes can bypass validators or field restrictions.
Patches
This issue has been patched in @adonisjs/lucid version 21.8.2 and 22.0.0-next.6. Please upgrade to this version or later.
Developers can mitigate this issue by strictly validating model inputs with an allow list that drops unknown keys if possible.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @adonisjs/lucid | all versions | 21.8.2npm install @adonisjs/lucid@21.8.2 |
| 📦npm | @adonisjs/lucid | ≥ 22.0.0-next.0&&< 22.0.0-next.6 | 22.0.0-next.6npm install @adonisjs/lucid@22.0.0-next.6 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @adonisjs/lucid, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @adonisjs/lucid to 21.8.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-22814 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-22814 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-22814. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-22814 in your dependencies?
O3 Security finds CVE-2026-22814 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.