CVE-2020-36830 is a medium severity (CVSS 4.3) inefficient regular expression flaw in nescalante urlregex up to 0.5.0, in index.js. A remote attacker can cause slow processing through backtracking. Upgrade to urlregex 0.5.1, which carries the patch commit e5a085a. The record says an exploit has been disclosed publicly.
What's affected
- urlregex up to and including 0.5.0.
- Fixed: 0.5.1, patch commit e5a085afe6abfaea1d1a78f54c45af9ef43ca1f9, per the record. The release page has no notes of its own.
The record scores it 4.3 (Medium) with vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L. 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 urlregex to see whether it is installed and at which version, directly or through another package. Lockfile search with grep urlregex package-lock.json also works.
What to do now
- Run
npm ls urlregexin each project. - Update with
npm install urlregex@0.5.1or the latest release. - If it comes in through another package, update that parent or use an override.
- Cap the length of strings passed to the matcher.
- Re-scan the repository.
After you patch, record the new version for urlregex 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. The pattern behind the URL matcher backtracks heavily on some input, so a long crafted string makes a Node.js process spend far too long on one request.
The record notes the issue was disclosed publicly. The score is moderate because the impact is availability only, but a single threaded server feels it.
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
What does the fix change?
The record points to patch commit e5a085a and version 0.5.1. The release page lists no notes, so read the commit if you need details.
How do I find every place urlregex 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://github.com/nescalante/urlregex/releases/tag/v0.5.1
- https://github.com/nescalante/urlregex/commit/e5a085afe6abfaea1d1a78f54c45af9ef43ca1f9
Last reviewed: 19 October 2026.