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 }).
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
- Replace the template rename target with a static string target.
- Keep the template but make the capture unable to produce
__proto__, using a negative lookahead:.rename(/^x-(?!__proto__$)(.+)$/, Joi.x('{#1}'), { multiple: true }) - Drop { multiple: true } from the rename, which stops the rename before the assignment.
Credited to Zyy0530, Str1ckl4nd, 7thParkk.
References
- https://github.com/hapijs/joi/security/advisories/GHSA-gg4h-3hg2-grpc
- https://nvd.nist.gov/vuln/detail/CVE-2026-84367
- https://github.com/hapijs/joi/pull/3134
- https://github.com/hapijs/joi/pull/3135
- https://github.com/hapijs/joi/commit/162f367aa178d2e1ebec8dc1164e5fe16536ddf6
- https://github.com/hapijs/joi/commit/172ececa192feda532b743d77bc9d3e523d19b01
- https://github.com/hapijs/joi/releases/tag/v17.13.5
- https://github.com/hapijs/joi/releases/tag/v18.2.4
- https://github.com/advisories/GHSA-gg4h-3hg2-grpc
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 entriesCVE-2026-118772
joi: quadratic-time split in `string().email({ multiple: true })` allows denial of service
high7.5No fixOct 30, 2026CVE-2026-92599
joi: Quadratic regular-expression backtracking in `Joi.string().isoDate()`
high7.5Sep 29, 2026CVE-2026-90771
joi messages compilation allows prototype replacement through __proto__ error codes
medium3.7Sep 13, 2026CVE-2026-84368
joi: Prototype pollution via a `__proto__` language key in custom messages
low3.7No fixSep 8, 2026CVE-2026-48038
joi has an uncaught RangeError on deeply nested input through recursive `link()` schemas
medium5.3Jun 11, 2026
