{"id":"GHSA-gg4h-3hg2-grpc","revision":"2a71e12995d54f81a5638d35e221e42e","records":[{"revision":"2a71e12995d54f81a5638d35e221e42e","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"GHSA-gg4h-3hg2-grpc","aliases":["CVE-2026-84367"],"title":"joi: object().rename() with a template target can set the validated object's prototype","description":"### Impact\n\nApplications 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.\n\nSchemas using a static string rename target are not affected, and neither are schemas left on the default `{ multiple: false }`.\n\n### Patches\n\nVersions 17.13.5 and 18.2.4 have been released to address the issue.\n\n### Workarounds\n\n1. Replace the template rename target with a static string target.\n2. Keep the template but make the capture unable to produce `__proto__`, using a negative lookahead: `.rename(/^x-(?!__proto__$)(.+)$/, Joi.x('{#1}'), { multiple: true })`\n3. Drop { multiple: true } from the rename, which stops the rename before the assignment.","state":0,"publishedAt":"2026-09-08T20:51:21+00:00","modifiedAt":"2026-09-08T21:00:05.0977097+00:00","affected":[{"ecosystem":"npm","name":"joi","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"16.0.0"},{"kind":"fixed","version":"17.13.5"}]}],"versions":[],"rawVersionEvidence":null},{"ecosystem":"npm","name":"joi","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"18.0.0"},{"kind":"fixed","version":"18.2.4"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V3","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"LOW"}],"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","https://github.com/hapijs/joi/releases/tag/v17.13.5","https://github.com/hapijs/joi/releases/tag/v18.2.4"],"sourceUrl":"https://github.com/advisories/GHSA-gg4h-3hg2-grpc","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-gg4h-3hg2-grpc","identifiers":["GHSA-gg4h-3hg2-grpc","CVE-2026-84367"]},"retained":false,"historicalAffected":[]}],"coverage":[]}