chore(deps): update dependency joi to v17.13.6 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
joi	17.13.3 → 17.13.6

---

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

• Pull request: fix: protect link recursion from max call stack hapijs/joi#3113

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

• https://github.com/hapijs/joi/security/advisories/GHSA-q7cg-457f-vx79
• https://github.com/hapijs/joi/pull/3113
• https://github.com/hapijs/joi/commit/2392713d3e9dd91ba752ac0c96e0eaf3d24b9a11
• https://github.com/advisories/GHSA-q7cg-457f-vx79

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

• https://github.com/hapijs/joi/security/advisories/GHSA-6w3j-5fw6-r9vr
• https://nvd.nist.gov/vuln/detail/CVE-2026-84368
• https://github.com/hapijs/joi/pull/3138
• https://github.com/hapijs/joi/pull/3139
• https://github.com/hapijs/joi/commit/8d0b808f3e874d28f9078f61b7742290989afb36
• https://github.com/hapijs/joi/commit/90d07571923c90e3432a328fc041d1cda03d30fa
• https://github.com/advisories/GHSA-6w3j-5fw6-r9vr

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

• https://github.com/hapijs/joi/security/advisories/GHSA-gg4h-3hg2-grpc
• https://nvd.nist.gov/vuln/detail/CVE-2026-84367
• https://github.com/hapijs/joi/pull/3134
• https://github.com/hapijs/joi/pull/3135
• https://github.com/hapijs/joi/commit/162f367aa178d2e1ebec8dc1164e5fe16536ddf6
• https://github.com/hapijs/joi/commit/172ececa192feda532b743d77bc9d3e523d19b01
• https://github.com/hapijs/joi/releases/tag/v17.13.5
• https://github.com/hapijs/joi/releases/tag/v18.2.4
• https://github.com/advisories/GHSA-gg4h-3hg2-grpc

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: Enabled.

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

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	joi@​17.13.3 ⏵ 17.13.4	+1	+2	+1	-5

View full report

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

Error: ERR_PNPM_UPDATE_VERSION_ON_INDIRECT_DEP

  × updating dependencies
  ╰─▶ "joi" (requested "17.13.6") is not a direct dependency, so the requested
      version cannot be recorded.
  help: An update resolves a transitive dependency the way a fresh install
        would, so a version on the command line has no effect on it. To pin
        one, add an override scoped to the range its dependents declare to
        pnpm-workspace.yaml:
        
          overrides:
            joi@<declared range>: 17.13.6
        
        To update it within the range its dependents already declare, drop the
        version: pnpm update joi