Safeguard
Vulnerability Analysis•

CVE-2020-26305: High ReDoS in CommonRegexJS

CVE-2020-26305 is a high ReDoS flaw in CommonRegexJS, all versions, no known patch. Avoid getLinks on untrusted text or replace the library.

Safeguard Security Team
3 min read

CVE-2020-26305 is a high severity (CVSS 7.5) regular expression denial of service flaw in CommonRegexJS, a JavaScript port of CommonRegex. The record says all available versions are affected and no patch was known. The advisory points at the links expression behind getLinks.

What's affected

  • CommonRegexJS, all available versions at publication.
  • Fixed: none known. Check issue 4 in the project repository for status.

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 commonregex 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

  1. Find CommonRegexJS in your projects.
  2. Locate calls to getLinks.
  3. Stop passing untrusted or very long text to it.
  4. Replace it with a vetted matcher with bounded runtime if you need link extraction.
  5. Track the upstream issue.

After you patch, record the new version for CommonRegexJS 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. The advisory ties the problem to the links regex used by getLinks.

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.

Quick check

Which function is affected?

The advisory points at the links regular expression used through getLinks. Other functions are not named in what I read.

How do I find every place CommonRegexJS 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

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.