CVE-2026-118772

waiting for further signalsZero needs more public information before it can validate it.

GHSA-4528-x5fx-h6hg ↗EUVD-2026-113320 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
hapijs joi >=17.1.1 <17.13.9; >=18.0.0 <18.3.1; >= 16.0.0
fixed in 18.3.1
CWE-1333 Inefficient Regular Expression Complexity
ETK-2026-2995Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:npm/joi
pkg:npm/@hapi/joi
4h 50msince last run
15mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h33m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Joi email validation using string().email({ multiple: true }) is affected when it accepts attacker-controlled input without an effective length limit. A crafted long value can consume excessive CPU time and delay other Node.js event-loop work. The issue requires use of the multiple-email validation option.

mitigation

Upgrade joi to version 18.3.1. Until upgrades are complete, enforce request-size limits before Joi validation and avoid applying the affected multiple-email rule to untrusted unbounded input.

fixed in 18.3.1

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
15m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-29 18:13Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-29 18:13Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-118772

{
  "etk_id": "ETK-2026-2995",
  "cve_id": "CVE-2026-118772",
  "display_id": "CVE-2026-118772",
  "ghsa_id": "GHSA-4528-x5fx-h6hg",
  "euvd_id": "EUVD-2026-113320",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Algorithmic denial of service in joi email validation",
  "summary": "Joi email validation using `string().email({ multiple: true })` is affected when it accepts attacker-controlled input without an effective length limit. A crafted long value can consume excessive CPU time and delay other Node.js event-loop work. The issue requires use of the multiple-email validation option.",
  "mitigation": "Upgrade joi to version 18.3.1. Until upgrades are complete, enforce request-size limits before Joi validation and avoid applying the affected multiple-email rule to untrusted unbounded input.",
  "vendor": "hapijs",
  "product": "joi",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">=17.1.1 <17.13.9",
        ">=18.0.0 <18.3.1"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "18.3.1"
      ],
      "package_name": "joi",
      "purl": "pkg:npm/joi"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 16.0.0"
      ],
      "ecosystem": "npm",
      "fixed_versions": [],
      "package_name": "@hapi/joi",
      "purl": "pkg:npm/@hapi/joi"
    }
  ],
  "cwes": [
    1333
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 14.554866633333333,
  "t0_at": "2026-10-29T18:13:33.771000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-29T18:13:33.771000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-29T18:13:33.771000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-118772"
    }
  }
}

published 2026-10-29 18:31Z
last change 2026-10-29 22:04Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.