NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2026-84367: joi: object().rename() with a template target can set the validated object's prototype

lowCVSS 3.1 3.7GHSA-gg4h-3hg2-grpc

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 }).

Published Sep 8, 2026

Affected packages

joi

Ecosystem
npm
Affected
>= 16.0.0, < 17.13.5
Fixed in
17.13.5
Check
npm ls joi

joi

Ecosystem
npm
Affected
>= 18.0.0, < 18.2.4
Fixed in
18.2.4
Check
npm ls joi

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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

  1. Replace the template rename target with a static string target.
  2. Keep the template but make the capture unable to produce __proto__, using a negative lookahead: .rename(/^x-(?!__proto__$)(.+)$/, Joi.x('{#1}'), { multiple: true })
  3. Drop { multiple: true } from the rename, which stops the rename before the assignment.

Credited to Zyy0530, Str1ckl4nd, 7thParkk.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More npm vulnerabilities

All npm entries