Vulnerability in joi (CVE-2026-48038)
Summary
Vulnerability in joi (CVE-2026-48038). Risk of unauthorized operations or information disclosure. Exploitable via RangeError. Mitigation: upgrade to 17.13.4 or later.
Original description
The description as published by the source.
joi is a schema description language and data validator for JavaScript. Prior to 17.13.4 and 18.2.1, denial of service is possible via an untrapped exception in services validating user-supplied JSON or object input with recursive link() schemas. When validate() is called without try/catch in a request handler, deeply nested input can trigger an unhandled RangeError and potentially crash the process; lower-impact paths using validateAsync() or try/catch produce a RangeError instead of a structured ValidationError. This issue is fixed in versions 17.13.4 and 18.2.1.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-48038 has been found in joi.
Attackers can target a specific entry point like RangeError over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade joi to 17.13.4 or later.
If unsure, ask your IT team or search "joi CVE-2026-48038" on the vendor's site.
CVE-2026-48038 (joi) — CWE-248 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: RangeError / ValidationError
Patched: 17.13.4 — apply immediately
Workaround: Try/catch the validation to avoid uncaught exceptions.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-248) exists in joi. Attackers reach the vulnerable code path via RangeError without authentication.
Check the vendor advisory for the affected versions of joi. Attack surface: RangeError / ValidationError.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to 17.13.4.
Workaround: Try/catch the validation to avoid uncaught exceptions.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'joi' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'joi' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
joiを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Try/catch the validation to avoid uncaught exceptions.パッチが適用されるまでの応急処置として、Try/catch the validation to avoid uncaught exceptions. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade joi to 17.13.4ステージング環境で 17.13.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- patch github.com
- web github.com
- web github.com