joi messages compilation allows prototype replacement through __proto__ error codesGHSA-wr44-6hxh-3jwq
LOWFix: hapijs/joi#3151GHSA-wr44-6hxh-3jwq is a low-severity (CVSS 3.7) CWE-1321 vulnerability in joi. A fix is available for joi — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-wr44-6hxh-3jwq.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-wr44-6hxh-3jwq by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
joinpmDescription
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | joi | all versions | 17.13.8npm install joi@17.13.8 |
| 📦npm | joi | ≥ 18.0.0&&< 18.2.9 | 18.2.9npm install joi@18.2.9 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for joi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update joi to 17.13.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wr44-6hxh-3jwq is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
A flaw in joi permits prototype manipulation when attacker-controlled JSON or configuration containing __proto__ is supplied to the .messages() or .prefs() APIs, potentially disrupting downstream application behavior.
Upgrade joi to 17.13.8, 18.2.9, or later. Avoid passing untrusted data to Joi message configuration until upgraded.Source: Red Hat security advisory for GHSA-wr44-6hxh-3jwq (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Hardened Images | grafana13-1-main-13.1.3-0.9.hum1 | RHSA-2026:67573 |
| Red Hat Hardened Images | grafana13-2-main-13.2.1-0.4.hum1 | RHSA-2026:67605 |
| Red Hat Hardened Images | grafana12-4-main-12.4.10-0.3.hum1 | RHSA-2026:67610 |
Frequently Asked Questions
Is GHSA-wr44-6hxh-3jwq in your dependencies?
Find it across npm, including transitive dependencies.