joi
Affected
- introduced
16.0.0, fixed17.13.5(semver)
Fixed versions
17.13.5
Fix
- Fixed version
17.13.5npm install [email protected]
Advisory
Also known as: CVE-2026-84367
joi: object().rename() with a template target can set the validated object's prototype
Impact
Applications are affected only if a schema renames keys with a regular-expression source and a Joi.expression() / Joi.x() target that interpolates the pattern's own match data, combined with { multiple: true }, for example .rename(/^x-(.+)$/, Joi.x('{#1}'), { multiple: true }). Because the target is rendered from the matched input key, an attacker who controls input keys can send x-__proto__ with an object value and make the rename target render as __proto__, which sets the prototype of the object joi returns instead of creating a key on it. The global Object.prototype is not modified, so the effect is confined to the object returned by that one validate() call.
Schemas using a static string rename target are not affected, and neither are schemas left on the default { multiple: false }.
Patches
Versions 17.13.5 and 18.2.4 have been released to address the issue.
Workarounds
__proto__, using a negative lookahead: .rename(/^x-(?!__proto__$)(.+)$/, Joi.x('{#1}'), { multiple: true })Low Basis: The source's own band: LOW
16.0.0, fixed 17.13.5 (semver)17.13.5
17.13.5npm install [email protected]18.0.0, fixed 18.2.4 (semver)18.2.4
18.2.4npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0