# CVE-2026-92599: Joi before 17.13.7 and 18.2.6 ReDoS via isoDate

> A remote attacker can cause a denial of service in applications using Joi by submitting a specially crafted ISO date string that triggers excessive regex processing.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** CLSA-2026-1790719586, ECHO-6a04-a4c8-a01f, GHSA-6h2x-m376-mqjq, MINI-3ccg-8x88-gjrr, MINI-442p-5382-wq2q, MINI-48j7-vm2r-cvj5, MINI-4mgc-xgp2-5p8j, MINI-5vq7-ghmv-27x4, MINI-9rr9-mcxr-7w37, MINI-cfm9-wqrv-47w8, MINI-cmfh-jh56-v64r, MINI-gj9r-3982-jvwq, MINI-mr8p-j5fc-f468, MINI-r73j-xc2g-jw58, MINI-rg74-v62x-6jpx, MINI-rjh2-7p67-w8g7, MINI-vg38-cmv6-h92v, MINI-vg8j-grq9-gr2j, MINI-vr8c-r32f-g6cw, MINI-vvq5-mqw3-f6h6, MINI-xg3x-9gjq-v563, ROOT-APP-NPM-CVE-2026-92599, ROOT-APP-NPM-GHSA-6h2x-m376-mqjq

## What is CVE-2026-92599?

CVE-2026-92599 is a high-severity denial of service vulnerability in hapijs joi, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-1333 (Inefficient Regular Expression Complexity)

## Which versions are affected by CVE-2026-92599?

4 open source packages ship an affected version, including joi.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `joi` | npm | From 17.2.0 | 17.13.7 |
| `joi` | npm | From 17.2.0 | 17.13.7 |
| `joi` | npm | From 18.0.0 | 18.2.6 |
| `joi` | npm | From 18.0.0 | 18.2.6 |

## How do I fix CVE-2026-92599?

Upgrade joi to a fixed version for your release line: 17.13.7 or 18.2.6.

## Is CVE-2026-92599 being exploited?

There is no known exploitation of CVE-2026-92599 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92599 and fix it if it is affected.

What it is: CVE-2026-92599 is a high-severity denial of service vulnerability in hapijs joi, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92599 in the wild and no public exploit code.

Affected packages and fixed versions:
- joi (npm): affected from 17.2.0; fixed in 17.13.7
- joi (npm): affected from 17.2.0; fixed in 17.13.7
- joi (npm): affected from 18.0.0; fixed in 18.2.6
- joi (npm): affected from 18.0.0; fixed in 18.2.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92599/ (Markdown: https://insights.sbomify.com/CVE-2026-92599/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92599
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92599
- OSV: https://osv.dev/vulnerability/CVE-2026-92599

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92599/
Summaries are generated and may contain mistakes; the official description above is the record.