{"answers":{"affected":"4 open source packages ship an affected version, including joi.","exploited":"There is no known exploitation of CVE-2026-84367 in the wild and no public exploit code.","fix":"Upgrade joi to a fixed version for your release line: 17.13.5 or 18.2.4.","what":"CVE-2026-84367 is a low-severity vulnerability in hapijs joi, published on 1 Sep 2026."},"fix_prompt":"Check this codebase for CVE-2026-84367 and fix it if it is affected.\n\nWhat it is: CVE-2026-84367 is a low-severity vulnerability in hapijs joi, published on 1 Sep 2026. \nExploitation: There is no known exploitation of CVE-2026-84367 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- joi (npm): affected from 16.0.0; fixed in 17.13.5\n- joi (npm): affected from 16.0.0; fixed in 17.13.5\n- joi (npm): affected from 18.0.0; fixed in 18.2.4\n- joi (npm): affected from 18.0.0; fixed in 18.2.4\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-84367/ (Markdown: https://insights.sbomify.com/CVE-2026-84367/index.md)","id":"CVE-2026-84367","markdown":"https://insights.sbomify.com/CVE-2026-84367/index.md","name":"CVE-2026-84367","record":{"aliases":["ECHO-b209-69fa-da03","GHSA-gg4h-3hg2-grpc","MINI-22wm-q4g5-j4pm","MINI-3hfp-4hhv-qqph","MINI-55hx-429w-7f6c","MINI-6p98-336j-pp7h","MINI-77pm-j5wx-mcr8","MINI-8m4w-prx6-w4rw","MINI-8wjw-rxfc-cjfv","MINI-f965-6jg8-f87v","MINI-fp7f-jqx3-xp8j","MINI-fx3q-5vrg-4rr6","MINI-gc2x-c8cg-r4hw","MINI-h3g3-q283-f9cg","MINI-h7g7-7wfr-2293","MINI-j763-c43j-2cj6","MINI-m5p6-c3hm-8899","MINI-mcf9-7hvj-66fg","MINI-p6g2-php4-3r22","MINI-rcr8-fg4p-jxm2","ROOT-APP-NPM-CVE-2026-84367"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"joi: object().rename() with a template target can set the validated object's prototype","id":"CVE-2026-84367","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":null,"year":"2026"},"n_packages":4,"n_references":5,"next":{"headline":"joi: Prototype pollution via a `__proto__` language key in custom messages","id":"CVE-2026-84368"},"packages":[{"ecosystem":"npm","fixed":["17.13.5"],"introduced":["16.0.0"],"last_affected":[],"package":"joi","purl":null,"source":"GHSA-gg4h-3hg2-grpc"},{"ecosystem":"npm","fixed":["17.13.5"],"introduced":["16.0.0"],"last_affected":[],"package":"joi","purl":"pkg:npm/joi","source":"GHSA-gg4h-3hg2-grpc"},{"ecosystem":"npm","fixed":["18.2.4"],"introduced":["18.0.0"],"last_affected":[],"package":"joi","purl":null,"source":"GHSA-gg4h-3hg2-grpc"},{"ecosystem":"npm","fixed":["18.2.4"],"introduced":["18.0.0"],"last_affected":[],"package":"joi","purl":"pkg:npm/joi","source":"GHSA-gg4h-3hg2-grpc"}],"prev":{"headline":"Scrapy: S3DownloadHandler sends signed S3 requests over plaintext HTTP by default","id":"CVE-2026-84366"},"products":["joi"],"published":"2026-09-01","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-03","vendors":["hapijs"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-84367/"}