Skip to content

Update dependency joi to v17.13.6 [SECURITY] - #5036

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-joi-vulnerability
Open

Update dependency joi to v17.13.6 [SECURITY]#5036
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-joi-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
joi 17.13.317.13.6 age confidence

joi has an uncaught RangeError on deeply nested input through recursive link() schemas

CVE-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:

  • Highest impact: validate() called without try/catch in a request handler would cause an unhandled exception, potentially crashing the process.
  • Lower impact: validateAsync() or validate() inside a try/catch, the validation fails, but the error type is RangeError rather than a structured ValidationError, complicating error handling.
Patches

Upgrade to version >= 18.2.1.

Workarounds

Try/catch the validation to avoid uncaught exceptions.

References

Severity

  • CVSS Score: 5.3 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

References

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 send x-__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 global Object.prototype is not modified, so the effect is confined to the object returned by that one validate() 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
  1. Replace the template rename target with a static string target.
  2. Keep the template but make the capture unable to produce __proto__, using a negative lookahead: .rename(/^x-(?!__proto__$)(.+)$/, Joi.x('{#​1}'), { multiple: true })
  3. Drop { multiple: true } from the rename, which stops the rename before the assignment.

Severity

  • CVSS Score: 3.7 / 10 (Low)
  • Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


joi: Prototype pollution via a __proto__ language key in custom messages

CVE-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 }) or rule({ message })) lets the attacker write properties onto Object.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 named constructor did the same to the Object function'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 }) or rule({ message }). Or validate that they don't contain any __proto__ or constructor property.

Severity

  • CVSS Score: 3.7 / 10 (Low)
  • Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

hapijs/joi (joi)

v17.13.6

Compare Source

v17.13.5

Compare Source

v17.13.4

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot requested a review from ajay-dhangar as a code owner July 8, 2026 06:41
@renovate renovate Bot added the dependencies label Jul 8, 2026

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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!

@deepsource-io

deepsource-io Bot commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

DeepSource Code Review

We reviewed changes in fd00972...cf87224 on this pull request. Below is the summary for the review, and you can see the individual issues we found as inline review comments.

See full review on DeepSource ↗

PR Report Card

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.

@github-actions

github-actions Bot commented Jul 8, 2026

Copy link
Copy Markdown

⚡️ Lighthouse Report for the Deploy Preview of this PR 🚀

🔗 Site: CodeHarborHub | Live Site

URL 🌐 Performance Accessibility Best Practices SEO 📊
/ 🔴 28 🟡 77 🟡 75 🟢 100 📄
/docs 🔴 47 🟡 87 🟢 96 🟢 100 📄
/courses 🟡 51 🟡 86 🟢 96 🟢 100 📄
/showcase 🔴 49 🟡 87 🟡 75 🟡 86 📄
/community 🟡 53 🟡 86 🟢 96 🟢 100 📄

@renovate
renovate Bot force-pushed the renovate/npm-joi-vulnerability branch from 453d4db to 5fb7f74 Compare July 30, 2026 16:10
@renovate
renovate Bot force-pushed the renovate/npm-joi-vulnerability branch 2 times, most recently from 61eb667 to 00664e9 Compare September 9, 2026 16:04
@renovate
renovate Bot force-pushed the renovate/npm-joi-vulnerability branch from 00664e9 to cf87224 Compare September 10, 2026 11:51
@renovate renovate Bot changed the title Update dependency joi to v17.13.4 [SECURITY] Update dependency joi to v17.13.6 [SECURITY] Sep 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant