Vulnerability in joi (CVE-2026-92599)
Summary
Vulnerability in joi (CVE-2026-92599). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 18.2.6 or later.
Original description
The description as published by the source.
joi (npm package joi, hapi.js) versions >=17.2.0 <17.13.7 and >=18.0.0 <18.2.6 are vulnerable to regular expression denial of service in the Joi.string().isoDate() validation rule. One of the regular expressions the rule applies to the input is unanchored, so a valid ISO date followed by a long run of fractional-second digits causes the regex engine to restart its search from every position in the string, yielding time proportional to the square of the input length (about 1.4 s for 64 KB of digits and about 22 s for 256 KB). A remote attacker who can supply a string to an isoDate validation can stall the application with a single request. Fixed in 17.13.7 and 18.2.6; as a workaround, cap the length of the string before it reaches joi.
Source: NIST National Vulnerability Database 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-92599 has been found in joi.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade joi to 18.2.6 or later.
If unsure, ask your IT team or search "joi CVE-2026-92599" on the vendor's site.
CVE-2026-92599 (joi) — CWE-1333 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 18.2.6 — apply immediately
Workaround: None except capping the length of the string before it reaches joi.
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-1333) exists in joi.
Check the vendor advisory for the affected versions of joi.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 18.2.6.
Workaround: None except capping the length of the string before it reaches joi.
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
None except capping the length of the string before it reaches joi.パッチが適用されるまでの応急処置として、None except capping the length of the string before it reaches joi. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade joi to 18.2.6ステージング環境で 18.2.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory vulncheck.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com