Prototype pollution via inherited custom-message language objects
Published Sep 1, 2026 · Updated Sep 2, 2026
Prototype pollution in @hapi/joi through 17.1.1, joi 17 before 17.13.6, and joi 18 before 18.2.5 lets attackers alter objects via custom messages. In lib/messages.js, exports.compile() and exports.merge() reuse inherited objects for attacker-controlled language keys, writing onto Object.prototype or Object function properties. Reachability requires a consuming application to pass untrusted input into schema-construction configuration; validated data alone cannot trigger the flaw, while successful pollution changes property tests process-wide.
Summary
What happened
Prototype pollution in @hapi/joi through 17.1.1, joi 17 before 17.13.6, and joi 18 before 18.2.5 lets attackers alter objects via custom messages. In lib/messages.js, exports.compile() and exports.merge() reuse inherited objects for attacker-controlled language keys, writing onto Object.prototype or Object function properties. Reachability requires a consuming application to pass untrusted input into schema-construction configuration; validated data alone cannot trigger the flaw, while successful pollution changes property tests process-wide.
The record
- CVE
- CVE-2026-84368
- Published
- Sep 1, 2026
- Updated
- Sep 2, 2026
- Vendor
- hapi.js
- Product
- joi
- Classifications
- CWE-1321, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 1, 2026CVE publishedPublication date reported by the CVE source.
- Sep 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 16.0.0, <= 17.1.1
- Affected versionversion=>= 17.2.0, < 17.13.6
- Affected versionversion=>= 18.0.0, < 18.2.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo