CVE-2026-84367
LOWDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 19% of all known CVEs.
References
Related Vulnerabilities
Other CWE-1321 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2019-0230 | Critical | 9.8 | 97% | - | - |
| CVE-2019-11358 | Medium | 6.1 | 87% | - | Fix |
| CVE-2020-7774 | High | 7.3 | 69% | - | Fix |
| CVE-2022-24760 | Critical | 10.0 | 49% | - | Fix |
| CVE-2022-39396 | Critical | 9.8 | 39% | - | Fix |
| CVE-2022-2564 | Critical | 9.8 | 33% | - | Fix |
Common questions
How do I fix CVE-2026-84367?
No published fix for CVE-2026-84367 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-84367 being actively exploited?
Not that we know of. CVE-2026-84367 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.27% is the estimated probability that it will be exploited in the next 30 days. That is higher than 19% of all scored CVEs.
How severe is CVE-2026-84367?
CVE-2026-84367 has a CVSS v3 base score of 3.7, rated low. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-84367
Markdown
[](https://tridentstack.com/cve/CVE-2026-84367)HTML
<a href="https://tridentstack.com/cve/CVE-2026-84367"><img src="https://tridentstack.com/cve/badge/CVE-2026-84367.svg" alt="CVE-2026-84367"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-09.