Skip to content

← Actionable
High, CVSS 8.2amended

Mass Assignment in AdonisJS Lucid Allows Overwriting Internal ORM State

CVE-2026-22814GHSA-g5gc-h5hp-555f

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@adonisjs/lucid 22.0.0-next.6, 21.8.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • npm @adonisjs/lucid

    Affected
    <= 21.8.1>= 22.0.0-next.0, < 22.0.0-next.6
    Fixed in
    22.0.0-next.6, 21.8.2

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.2 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-22814: 0.54% estimated exploitation activity in the next 30 days; percentile 45.26 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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)…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-g5gc-h5hp-555f

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-g5gc-h5hp-555f

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-22814

Advisory: Mass Assignment in AdonisJS Lucid Allows Overwriting Internal ORM State
IDs: CVE-2026-22814, GHSA-g5gc-h5hp-555f
Record: https://patchnext.com/advisories/cve-2026-22814 (revision 3, source checked 26 Oct 2026, 12:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @adonisjs/lucid 22.0.0-next.6, 21.8.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @adonisjs/lucid: affected <= 21.8.1; >= 22.0.0-next.0, < 22.0.0-next.6; fixed in 22.0.0-next.6, 21.8.2

## Suggested inspection (read-only)
- `npm ls @adonisjs/lucid --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @adonisjs/lucid.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-g5gc-h5hp-555f (OSV record GHSA-g5gc-h5hp-555f lists affected ranges: npm @adonisjs/lucid >=0 =22.0.0-next.0 <22.0.0-next.6 (fixed))
- Verified: https://github.com/advisories/GHSA-g5gc-h5hp-555f (GitHub-reviewed advisory GHSA-g5gc-h5hp-555f lists affected ranges: npm @adonisjs/lucid >=0 =22.0.0-next.0 <22.0.0-next.6)

Commands are suggestions: review each one before running it.

Loading voting…