joi before versions 17.13.8 and 18.2.9 contains a prototype pollution vulnerability in the messages compilation function that accepts __proto__ as an error code. Attackers can supply __proto__ keys in custom messages to replace the returned object's prototype, breaking downstream code relying on Object.prototype methods.
CVE-2026-90771
Score 3.7 from GitHub Security Advisory published 2026-09-13. a secondary CVSS source baseline 3.7; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 3.7
- EG Score
- 3.7(high)
- EG Risk
- 33(Track)EG Risk 33/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 computedSeverity37% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 18%
- KEV
- Not listed
Published
September 13, 2026
Last Modified
September 16, 2026
References (6)
- disclosure@vulncheckhttps://github.com/hapijs/joi
- disclosure@vulncheckhttps://github.com/hapijs/joi/blob/v18.2.8/lib/messages.js
- disclosure@vulncheckhttps://github.com/hapijs/joi/commit/5b8333c9177e08b4ef4ed02903c2d657084e7afb
- disclosure@vulncheckhttps://github.com/hapijs/joi/issues/3150
- disclosure@vulncheckhttps://www.vulncheck.com/advisories/joi-before-17.13.8-and-18.2.9-prototype-pollution-via-messages
- 134c704f-9b21-4f2e-91b3-4a467353bcc0https://github.com/hapijs/joi/issues/3150
Vendor Advisories for CVE-2026-90771(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 14× 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.
- 2026-09-19 19:46 UTCEG score recompute
- 2026-09-19 19:46 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-16 15:30 UTCEG score recompute
- 2026-09-16 15:30 UTCGHSA enrichment
- 2026-09-16 14:26 UTCEG score recompute
- 2026-09-16 14:26 UTCGHSA enrichment
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-13 11:21 UTCEG score recompute
- 2026-09-13 10:50 UTCEG score recompute
- 2026-09-13 10:49 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-1321
- CVE-2020-12079EG 10.0CRITICAL
- CVE-2011-10019EG 9.8EPSS p90CRITICAL
- CVE-2020-28462NVD 7.3EG 9.8CRITICAL
- CVE-2020-28276EG 9.8CRITICAL
- CVE-2020-28271EG 9.8CRITICAL
- CVE-2020-28270EG 9.8EPSS p90CRITICAL
- CVE-2020-28269EG 9.8EPSS p90CRITICAL
- CVE-2020-8158EG 9.8CRITICAL
- CVE-2019-0230EG 9.8EPSS p100CRITICAL
- CVE-2020-7727EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-90771?
When was CVE-2026-90771 disclosed?
Is CVE-2026-90771 actively exploited?
What is the CVSS score of CVE-2026-90771?
How do I remediate CVE-2026-90771?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-90771
Is Your Infrastructure Affected by CVE-2026-90771?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.