Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.7amended

joi: Quadratic regular-expression backtracking in Joi.string().isoDate()

CVE-2026-92599GHSA-6h2x-m376-mqjq

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (joi 18.2.6, 17.13.7), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm joi

    Affected
    >= 17.2.0, < 17.13.7>= 18.0.0, < 18.2.6
    Fixed in
    17.13.7, 18.2.6

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
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 · score source
EPSS
  • CVE-2026-92599: 0.58% estimated exploitation activity in the next 30 days; percentile 47.83 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact Any application that validates a user-supplied string with Joi.string().isoDate() can be stalled by a single request. One of the regular expressions the rule runs over the input was unanchored, so a valid ISO date followed by a long run of fractional-second digits made the regex engine restart its search from every position in the string, costing time proportional to the square of the input length. 64 KB of digits costs about 1.4 s and 256 KB about 22 s. Patches Upgrade to version 17.13.7 or 18.2.6 depending on your current major version. Workarounds None except capping the length of the string before it reaches joi.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-6h2x-m376-mqjq

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GHSA-6h2x-m376-mqjq

  4. Revision 1 · created ·

    Published from ghsa record GHSA-6h2x-m376-mqjq

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-92599

Advisory: joi: Quadratic regular-expression backtracking in `Joi.string().isoDate()`
IDs: CVE-2026-92599, GHSA-6h2x-m376-mqjq
Record: https://patchnext.com/advisories/cve-2026-92599 (revision 4, source checked 26 Oct 2026, 13:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: joi 18.2.6, 17.13.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm joi: affected >= 17.2.0, < 17.13.7; >= 18.0.0, < 18.2.6; fixed in 17.13.7, 18.2.6

## Suggested inspection (read-only)
- `npm ls joi --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on joi.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-6h2x-m376-mqjq (GitHub-reviewed advisory GHSA-6h2x-m376-mqjq lists affected ranges: npm joi >=17.2.0 =18.0.0 <18.2.6)
- Verified: https://osv.dev/vulnerability/GHSA-6h2x-m376-mqjq (OSV record GHSA-6h2x-m376-mqjq lists affected ranges: npm joi >=17.2.0 =18.0.0 <18.2.6 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…