# CVE-2026-92599 — hapijs joi

> As of 2026-09-16, CVE-2026-92599 is a HIGH-severity vulnerability in hapijs joi, CVSS v3.1 7.5. No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-92599 as of 2026-09-16; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-09-16

## What is CVE-2026-92599?

joi (npm package `joi`, hapi.js) versions >=17.2.0 =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.

The record classifies CVE-2026-92599 under weakness class [CWE-1333](https://cwe.mitre.org/data/definitions/1333.html). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 19 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 7.5 — HIGH (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **CVSS v4.0 base score:** 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`)
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 3.8/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-09-16

## Is CVE-2026-92599 being exploited?

It currently carries a trending score of 30 in the Threadlinqs vulnerability feed.

## Affected products and versions

- **hapijs**: joi

## How to fix CVE-2026-92599

No vendor patch reference has been recorded for CVE-2026-92599 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-92599

No threat campaign in the Threadlinqs corpus currently references CVE-2026-92599, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD. Last verified by Threadlinqs on 2026-09-17. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com — vendor advisory](https://github.com/hapijs/joi/security/advisories/GHSA-6h2x-m376-mqjq)

**Third-party advisory**

- [vulncheck.com — third party advisory](https://www.vulncheck.com/advisories/joi-before-17.13.7-and-18.2.6-redos-via-isodate)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-92599
Full detection coverage and IOCs for threats exploiting CVE-2026-92599 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp