Update dependency joi to v17.13.6 [SECURITY] - #5036
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
There was a problem hiding this comment.
Great job, @renovate[bot]! 🎉 Thank you for submitting your pull request to CodeHarborHub. We appreciate your contribution and enthusiasm! Our team will review it soon. If you have any questions or need further assistance, feel free to reach out. Thanks for contributing!
Contributor
|
|
Overall Grade |
Security Reliability Complexity Hygiene |
Code Review Summary
| Analyzer | Status | Updated (UTC) | Details |
|---|---|---|---|
| JavaScript | Sep 10, 2026 11:51a.m. | Review ↗ |
Important
AI Review is run only on demand for your team. We're only showing results of static analysis review right now. To trigger AI Review, comment @deepsourcebot review on this thread.
renovate
Bot
force-pushed
the
renovate/npm-joi-vulnerability
branch
from
July 30, 2026 16:10
453d4db to
5fb7f74
Compare
renovate
Bot
force-pushed
the
renovate/npm-joi-vulnerability
branch
2 times, most recently
from
September 9, 2026 16:04
61eb667 to
00664e9
Compare
renovate
Bot
force-pushed
the
renovate/npm-joi-vulnerability
branch
from
September 10, 2026 11:51
00664e9 to
cf87224
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
17.13.3→17.13.6joi has an uncaught RangeError on deeply nested input through recursive
link()schemasCVE-2026-48038 / GHSA-q7cg-457f-vx79
More information
Details
Impact
Denial of service via untrapped exception in services validating user-supplied JSON / object input with recursive link schemas.
The blast radius depends on how the application invokes joi:
validate()called withouttry/catchin a request handler would cause an unhandled exception, potentially crashing the process.validateAsync()orvalidate()inside atry/catch, the validation fails, but the error type isRangeErrorrather than a structuredValidationError, complicating error handling.Patches
Upgrade to version >= 18.2.1.
Workarounds
Try/catch the validation to avoid uncaught exceptions.
References
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
joi: object().rename() with a template target can set the validated object's prototype
CVE-2026-84367 / GHSA-gg4h-3hg2-grpc
More information
Details
Impact
Applications are affected only if a schema renames keys with a regular-expression source and a
Joi.expression()/Joi.x()target that interpolates the pattern's own match data, combined with{ multiple: true }, for example.rename(/^x-(.+)$/, Joi.x('{#​1}'), { multiple: true }). Because the target is rendered from the matched input key, an attacker who controls input keys can sendx-__proto__with an object value and make the rename target render as__proto__, which sets the prototype of the object joi returns instead of creating a key on it. The globalObject.prototypeis not modified, so the effect is confined to the object returned by that onevalidate()call.Schemas using a static string rename target are not affected, and neither are schemas left on the default
{ multiple: false }.Patches
Versions 17.13.5 and 18.2.4 have been released to address the issue.
Workarounds
__proto__, using a negative lookahead:.rename(/^x-(?!__proto__$)(.+)$/, Joi.x('{#​1}'), { multiple: true })Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
joi: Prototype pollution via a
__proto__language key in custom messagesCVE-2026-84368 / GHSA-6w3j-5fw6-r9vr
More information
Details
Impact
An application that passes attacker-controlled data into joi's custom message configuration (
messages(),message(),prefs({ messages }),Joi.extend({ messages })orrule({ message })) lets the attacker write properties ontoObject.prototype, where every object in the process then inherits them. A key named__proto__was treated as a language name, and the code reused the object it found at that key, which resolves to the prototype rather than to a new own property; a key namedconstructordid the same to theObjectfunction's statics. A consuming application that gates on the mere presence of a property (if (user.isAdmin)) can be made to take the wrong branch for every object it inspects.This is not reachable from data that joi validates. Custom messages are schema-construction configuration, normally written by the application developer. Exploitation therefore requires an application that feeds untrusted input straight into schema construction.
Patches
Upgrade to version 18.2.5 or 17.13.6.
Workarounds
Do not pass untrusted input into
messages(),message(),prefs({ messages }),Joi.extend({ messages })orrule({ message }). Or validate that they don't contain any__proto__orconstructorproperty.Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
hapijs/joi (joi)
v17.13.6Compare Source
v17.13.5Compare Source
v17.13.4Compare Source
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.