CVE-2026-92599

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-17. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

September 16, 2026

Last Modified

September 18, 2026

Advisory Details (2)

Auto-updated Sep 16, 2026
Patch available. Sources: github.
generic

Joi before 17.13.7 and 18.2.6 ReDoS via isoDate | Advisories | VulnCheck

https://www.vulncheck.com/advisories/joi-before-17.13.7-and-18.2.6-redos-via-isodate
github Patch Available

Quadratic regular-expression backtracking in `Joi.string().isoDate()` · Advisory · hapijs/joi · GitHub

https://github.com/hapijs/joi/security/advisories/GHSA-6h2x-m376-mqjq

Vendor Advisories for CVE-2026-92599(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 15× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 09:16 UTCGHSA enrichment
  2. 2026-09-18 20:35 UTCEG score recompute
  3. 2026-09-18 20:35 UTCGHSA enrichment
  4. 2026-09-18 20:10 UTCEG score recompute
  5. 2026-09-18 20:10 UTCGHSA enrichment
  6. 2026-09-18 19:28 UTCEPSS rescore
  7. 2026-09-18 12:24 UTCGHSA enrichment
  8. 2026-09-17 23:44 UTCEG score recompute
  9. 2026-09-17 23:44 UTCGHSA enrichment
  10. 2026-09-17 19:32 UTCEPSS rescore
  11. 2026-09-17 11:05 UTCEG score recompute
  12. 2026-09-17 11:05 UTCGHSA enrichment
  13. 2026-09-16 22:25 UTCEG score recompute
  14. 2026-09-16 21:54 UTCEG score recompute
  15. 2026-09-16 21:54 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-92599?
CVE-2026-92599 is a high vulnerability published on September 16, 2026. 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…
When was CVE-2026-92599 disclosed?
CVE-2026-92599 was first published in the National Vulnerability Database on September 16, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92599 actively exploited?
CVE-2026-92599 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 72.5% of all scored CVEs.
What is the CVSS score of CVE-2026-92599?
CVE-2026-92599 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-92599?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-92599, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-92599

Explore →

Is Your Infrastructure Affected by CVE-2026-92599?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs