← Back
CVE-2026-48038
medium
CVSS 5.3
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**A vulnerability** (CWE-248) exists in joi. Attackers reach the vulnerable code path via ``RangeError`` without authentication.
📍 Affected scope
joi — . Attack surface: `RangeError` / `ValidationError`.
🔥 Severity
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **17.13.4**.
🛡️ Workaround
Workaround: Try/catch the validation to avoid uncaught exceptions.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Try/catch the validation to avoid uncaught exceptions.パッチが適用されるまでの応急処置として、Try/catch the validation to avoid uncaught exceptions. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade joi to 17.13.4ステージング環境で 17.13.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
joi
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"17.13.4"}]}]
References
- package https://github.com/hapijs/joi
- web https://github.com/hapijs/joi/security/advisories/GHSA-q7cg-457f-vx79
- web https://github.com/hapijs/joi/pull/3113
- web https://github.com/hapijs/joi/commit/2392713d3e9dd91ba752ac0c96e0eaf3d24b9a11
- web https://github.com/advisories/GHSA-q7cg-457f-vx79
- web [email protected]
- web [email protected]