CVE-2026-92599
HIGHDescription
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.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Exploit Intelligence
Moderate risk: more likely to be exploited than 46% of all known CVEs.
References
Related Vulnerabilities
Other CWE-1333 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2023-3364 | High | 7.5 | 44% | - | Fix |
| CVE-2024-8124 | High | 7.5 | 40% | - | Fix |
| CVE-2024-25126 | Medium | 5.3 | 35% | - | Fix |
| CVE-2024-2651 | Medium | 6.5 | 33% | - | Fix |
| CVE-2021-32837 | High | 7.5 | 29% | - | Fix |
| CVE-2024-2829 | High | 7.5 | 26% | - | Fix |
Common questions
How do I fix CVE-2026-92599?
Upgrade joi to 17.13.7 or later.
Is CVE-2026-92599 being actively exploited?
Not that we know of. CVE-2026-92599 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.58% is the estimated probability that it will be exploited in the next 30 days. That is higher than 46% of all scored CVEs.
How severe is CVE-2026-92599?
CVE-2026-92599 has a CVSS v3 base score of 7.5, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-92599 affect?
Published advisories record a fix for joi (npm). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-92599
Markdown
[](https://tridentstack.com/cve/CVE-2026-92599)HTML
<a href="https://tridentstack.com/cve/CVE-2026-92599"><img src="https://tridentstack.com/cve/badge/CVE-2026-92599.svg" alt="CVE-2026-92599"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-22.