GHSA-XX4C-JJ58-R7X6

GHSA-XX4C-JJ58-R7X6 is a medium-severity inefficient regular expression (ReDoS) vulnerability in validator (npm), affecting versions >= 11.1.0, < 13.7.0. It is fixed in 13.7.0.

Summary

Inefficient Regular Expression Complexity in Validator.js

Impact

Versions of validator prior to 13.7.0 are affected by an inefficient Regular Expression complexity when using the rtrim and trim sanitizers.

A regular expression with worst-case exponential or polynomial matching time is applied to untrusted input, causing excessive CPU use. Typical impact: denial of service when input is crafted to trigger backtracking.

GHSA-XX4C-JJ58-R7X6 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (13.7.0); upgrading removes the vulnerable code path.

Affected versions

validator (>= 11.1.0, < 13.7.0)

Security releases

validator → 13.7.0 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

The problem has been patched in validator 13.7.0

Frequently Asked Questions

  1. What is GHSA-XX4C-JJ58-R7X6? GHSA-XX4C-JJ58-R7X6 is a medium-severity inefficient regular expression (ReDoS) vulnerability in validator (npm), affecting versions >= 11.1.0, < 13.7.0. It is fixed in 13.7.0. A regular expression with worst-case exponential or polynomial matching time is applied to untrusted input, causing excessive CPU use.
  2. How severe is GHSA-XX4C-JJ58-R7X6? GHSA-XX4C-JJ58-R7X6 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of validator are affected by GHSA-XX4C-JJ58-R7X6? validator (npm) versions >= 11.1.0, < 13.7.0 is affected.
  4. Is there a fix for GHSA-XX4C-JJ58-R7X6? Yes. GHSA-XX4C-JJ58-R7X6 is fixed in 13.7.0. Upgrade to this version or later.
  5. Is GHSA-XX4C-JJ58-R7X6 exploitable, and should I be worried? Whether GHSA-XX4C-JJ58-R7X6 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether GHSA-XX4C-JJ58-R7X6 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix GHSA-XX4C-JJ58-R7X6? Upgrade validator to 13.7.0 or later.

Other vulnerabilities in validator

Stop the waste.
Protect your environment with Kodem.