CVE-2020-26308 is a high severity (CVSS 7.5) regular expression denial of service flaw in validate.js, a declarative validation library. Versions 0.13.1 and prior are affected, and the record said no patch was known. GitHub Security Lab points at the email validation pattern.
What's affected
- validate.js 0.13.1 and prior, per the record.
- Fixed: none stated. Check issue 342 upstream.
The record scores it 7.5 (High) with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. The record does not flag it as a CISA Known Exploited Vulnerability, and none of the pages I read report exploitation in the wild.
How to check if you're exposed
Run npm ls --all | grep -i validate.js in your project to see whether it is a direct or transitive dependency. A lockfile search works too. You can also paste your manifest into the free scanner at gold.safeguard.sh/scan.
What to do now
- Find validate.js in lockfiles.
- Check whether you use the email validator.
- Limit the length of email strings before validation.
- Move to a validator that avoids unbounded backtracking if no fix is released.
After you patch, record the new version for validate.js in your asset inventory, and confirm it with the same check you used above. A fix that was never verified is easy to forget, and an inventory that shows versions is what lets you answer the next advisory in minutes instead of days.
Why it matters
The record maps this to CWE-1333, inefficient regular expression complexity. A pattern that backtracks without bound can take exponential time on a crafted string, so a single request can tie up a Node.js process, which is single threaded. GitHub Security Lab found these with a CodeQL query and published the advisory in July 2021 after a disclosure deadline expired. In validate.js the advisory names the email validation PATTERN expression.
To check open source components in your own projects for known CVEs like this one, try the free in-browser dependency scan at gold.safeguard.sh/scan, or look the CVE up in the Gold directory.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
How can input length help?
Exponential backtracking grows with input length, so a short cap on the string size limits the damage even before a fix.
How do I find every place validate.js is used?
Start with an inventory of installed software and versions, because you cannot patch what you have not found. Check servers, build hosts, test copies and anything a vendor bundles. For open source libraries, a dependency scan or SBOM gives the same list for your code.
Sources
- https://securitylab.github.com/advisories/GHSL-2020-302-redos-validate.js/
- https://github.com/ansman/validate.js/issues/342
Last reviewed: 19 October 2026.