CVE-2026-84367

published 1 Sep 2026 · updated 3 Sep 2026

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

3.7LowCVSS 3.7EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

joi is a schema description language and data validator for JavaScript. From 16.0.0 until 17.13.5 and 18.2.4, joi's lib/types/keys.js internals.rename() implementation used by object().rename() permits a schema that renames keys with a regular-expression source and a Joi.expression() or Joi.x() target that interpolates the pattern's own match data, combined with { multiple: true }, to derive a target from an attacker-controlled input key. An attacker can send x-__proto__ with an object value, causing the target to render as __proto__ and set the prototype of the object returned by validate() instead of creating an own key. The global Object.prototype is not modified, so the effect is confined to the object returned by that validation call. Static-string targets and schemas using the default { multiple: false } are not affected. This issue is fixed in versions 17.13.5 and 18.2.4.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
hapijs>=16.0.0 <17.13.5, >=18.0.0 <18.2.4

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-84367 severity on Zeptric[![CVE-2026-84367](https://zeptric.io/badge/cve/CVE-2026-84367.svg)](https://zeptric.io/cve/CVE-2026-84367)