GHSA-g5gc-h5hp-555f
GHSA-g5gc-h5hp-555f is a CWE-915 vulnerability in @adonisjs/lucid. O3 Security confirms whether GHSA-g5gc-h5hp-555f is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Mass Assignment in AdonisJS Lucid Allows Overwriting Internal ORM State
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
@adonisjs/lucid📦@adonisjs/lucidReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.
Description
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.2 |
| 📦npm | @adonisjs/lucid | ≥ 22.0.0-next.0&&< 22.0.0-next.6 | 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @adonisjs/lucid to 21.8.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g5gc-h5hp-555f 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 pinpoints whether GHSA-g5gc-h5hp-555f is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-g5gc-h5hp-555f. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-g5gc-h5hp-555f in your dependencies?
O3 detects GHSA-g5gc-h5hp-555f across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.