CVE-2026-84367

LOWPre-NVD 3.73.7—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 3.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
3.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
3.7
EG Score
3.7(medium)
EG Risk
17(Track)
EG Risk 17/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity37% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
19%
KEV
Not listed

Published

September 1, 2026

Last Modified

September 9, 2026

References (5)

Vendor Advisories for CVE-2026-84367(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
joi—18.2.4—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 11:58 UTCEG score recompute
  3. 2026-09-17 19:32 UTCEPSS rescore
  4. 2026-09-16 14:09 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-15 15:05 UTCEG score recompute
  7. 2026-09-15 03:12 UTCEPSS rescore
  8. 2026-09-15 03:12 UTCEPSS rescore
  9. 2026-09-12 18:05 UTCEG score recompute
  10. 2026-09-11 14:53 UTCEPSS rescore
  11. 2026-09-11 14:53 UTCEPSS rescore
  12. 2026-09-09 10:32 UTCEG score recompute
  13. 2026-09-08 22:01 UTCEPSS rescore
  14. 2026-09-06 13:48 UTCEPSS rescore
  15. 2026-09-06 13:26 UTCEG score recompute
  16. 2026-09-05 15:31 UTCEPSS rescore
  17. 2026-09-04 05:07 UTCEPSS rescore
  18. 2026-09-03 16:33 UTCEG score recompute
  19. 2026-09-03 16:04 UTCEG score recompute
  20. 2026-09-02 14:12 UTCEPSS rescore
  21. 2026-09-01 21:26 UTCEG score recompute
  22. 2026-09-01 20:43 UTCEG score recompute
  23. 2026-09-01 20:42 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-84367?
CVE-2026-84367 is a low vulnerability published on September 1, 2026. 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()…
When was CVE-2026-84367 disclosed?
CVE-2026-84367 was first published in the National Vulnerability Database on September 1, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-84367 actively exploited?
CVE-2026-84367 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 80.6% of all scored CVEs.
What is the CVSS score of CVE-2026-84367?
CVE-2026-84367 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2026-84367?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-84367, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-84367

Explore →

Is Your Infrastructure Affected by CVE-2026-84367?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs