CVE-2026-84367: joi: object().rename() with a template target can set the validated object's prototype
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 }.
References
- github.com/advisories/GHSA-gg4h-3hg2-grpc
- github.com/hapijs/joi/commit/162f367aa178d2e1ebec8dc1164e5fe16536ddf6
- github.com/hapijs/joi/commit/172ececa192feda532b743d77bc9d3e523d19b01
- github.com/hapijs/joi/pull/3134
- github.com/hapijs/joi/pull/3135
- github.com/hapijs/joi/releases/tag/v17.13.5
- github.com/hapijs/joi/releases/tag/v18.2.4
- github.com/hapijs/joi/security/advisories/GHSA-gg4h-3hg2-grpc
- nvd.nist.gov/vuln/detail/CVE-2026-84367
Code Behaviors & Features
Detect and mitigate CVE-2026-84367 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →