FKIE_CVE-2026-118772

Vulnerability from fkie_nvd - Published: 2026-10-29 19:17 - Updated: 2026-10-30 19:37
Severity
7.5 (High) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Summary
joi is a schema description language and data validator for JavaScript. From 17.1.1 until 17.13.9 and 18.3.1, the Joi.string().email({ multiple: true }) rule uses a separator regular expression whose leading whitespace quantifier is retried at every position in a long whitespace run that contains no separator, causing quadratic work during String.prototype.split. The behavior applies to the default separator and every custom separator. Applications that validate attacker-controlled values with the multiple option and no effective prior length limit can have the Node.js event loop blocked for seconds by one request, preventing other work. A .max() rule is not sufficient when abortEarly: false allows the email rule to run after the maximum-length check fails. This vulnerability is fixed in versions 17.13.9 and 18.3.1.
References
security-advisories@github.comhttps://github.com/hapijs/joi/commit/03dc1d909818503b06240dadc81e9227ed2649cf
security-advisories@github.comhttps://github.com/hapijs/joi/commit/807858d7480f5075b0610817e3e44230890fb18e
security-advisories@github.comhttps://github.com/hapijs/joi/pull/3162
security-advisories@github.comhttps://github.com/hapijs/joi/pull/3163
security-advisories@github.comhttps://github.com/hapijs/joi/releases/tag/v17.13.9
security-advisories@github.comhttps://github.com/hapijs/joi/releases/tag/v18.3.1
security-advisories@github.comhttps://github.com/hapijs/joi/security/advisories/GHSA-4528-x5fx-h6hg
Impacted products
Vendor Product Version
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "product": "joi",
          "vendor": "hapijs",
          "versions": [
            {
              "status": "affected",
              "version": "\u003e= 16.0.0, \u003c= 17.1.1"
            },
            {
              "status": "affected",
              "version": "\u003e= 18.0.0, \u003c 18.3.1"
            }
          ]
        },
        {
          "product": "joi",
          "vendor": "@hapi",
          "versions": [
            {
              "status": "affected",
              "version": "\u003e= 16.0.0, \u003c= 17.1.1"
            }
          ]
        }
      ],
      "source": "security-advisories@github.com"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "joi is a schema description language and data validator for JavaScript. From 17.1.1 until 17.13.9 and 18.3.1, the Joi.string().email({ multiple: true }) rule uses a separator regular expression whose leading whitespace quantifier is retried at every position in a long whitespace run that contains no separator, causing quadratic work during String.prototype.split. The behavior applies to the default separator and every custom separator. Applications that validate attacker-controlled values with the multiple option and no effective prior length limit can have the Node.js event loop blocked for seconds by one request, preventing other work. A .max() rule is not sufficient when abortEarly: false allows the email rule to run after the maximum-length check fails. This vulnerability is fixed in versions 17.13.9 and 18.3.1."
    }
  ],
  "id": "CVE-2026-118772",
  "lastModified": "2026-10-30T19:37:07.073",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "HIGH",
          "baseScore": 7.5,
          "baseSeverity": "HIGH",
          "confidentialityImpact": "NONE",
          "integrityImpact": "NONE",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
          "version": "3.1"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 3.6,
        "source": "security-advisories@github.com",
        "type": "Secondary"
      }
    ]
  },
  "published": "2026-10-29T19:17:19.563",
  "references": [
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/hapijs/joi/commit/03dc1d909818503b06240dadc81e9227ed2649cf"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/hapijs/joi/commit/807858d7480f5075b0610817e3e44230890fb18e"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/hapijs/joi/pull/3162"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/hapijs/joi/pull/3163"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/hapijs/joi/releases/tag/v17.13.9"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/hapijs/joi/releases/tag/v18.3.1"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/hapijs/joi/security/advisories/GHSA-4528-x5fx-h6hg"
    }
  ],
  "sourceIdentifier": "security-advisories@github.com",
  "vulnStatus": "Awaiting Analysis",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-1333"
        }
      ],
      "source": "security-advisories@github.com",
      "type": "Primary"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.