CVE-2026-84368: joi: Prototype pollution via a `__proto__` language key in custom messages
Impact An application that passes attacker-controlled data into joi's custom message configuration (messages(), message(), prefs({ messages }), Joi.extend({ messages }) or rule({ message })) lets the attacker write properties onto Object.prototype, where every object in the process then inherits them.
Published Sep 8, 2026
Affected packages
joi
- Ecosystem
- npm
- Affected
- >= 17.2.0, < 17.13.6
- Fixed in
- 17.13.6
- Check
npm ls joi
@hapi/joi
- Ecosystem
- npm
- Affected
- >= 16.0.0, <= 17.1.1
- Fixed in
- No patched version yet
- Check
npm ls @hapi/joi
joi
- Ecosystem
- npm
- Affected
- >= 18.0.0, < 18.2.5
- Fixed in
- 18.2.5
- Check
npm ls joi
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
An application that passes attacker-controlled data into joi's custom message configuration (messages(), message(), prefs({ messages }), Joi.extend({ messages }) or rule({ message })) lets the attacker write properties onto Object.prototype, where every object in the process then inherits them. A key named __proto__ was treated as a language name, and the code reused the object it found at that key, which resolves to the prototype rather than to a new own property; a key named constructor did the same to the Object function's statics. A consuming application that gates on the mere presence of a property (if (user.isAdmin)) can be made to take the wrong branch for every object it inspects.
This is not reachable from data that joi validates. Custom messages are schema-construction configuration, normally written by the application developer. Exploitation therefore requires an application that feeds untrusted input straight into schema construction.
Patches
Upgrade to version 18.2.5 or 17.13.6.
Workarounds
Do not pass untrusted input into messages(), message(), prefs({ messages }), Joi.extend({ messages }) or rule({ message }). Or validate that they don't contain any __proto__ or constructor property.
Credited to tihanyin, mordamin.
References
- https://github.com/hapijs/joi/security/advisories/GHSA-6w3j-5fw6-r9vr
- https://nvd.nist.gov/vuln/detail/CVE-2026-84368
- https://github.com/hapijs/joi/pull/3138
- https://github.com/hapijs/joi/pull/3139
- https://github.com/hapijs/joi/commit/8d0b808f3e874d28f9078f61b7742290989afb36
- https://github.com/hapijs/joi/commit/90d07571923c90e3432a328fc041d1cda03d30fa
- https://github.com/advisories/GHSA-6w3j-5fw6-r9vr
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-84367
joi: object().rename() with a template target can set the validated object's prototype
low3.7Sep 8, 2026CVE-2026-48038
joi has an uncaught RangeError on deeply nested input through recursive `link()` schemas
medium5.3Jun 11, 2026
