Safeguard
Vulnerability Analysis•

CVE-2020-26304: High ReDoS in Foundation Sites

CVE-2020-26304 is a high ReDoS flaw in Foundation Sites 6.3.3 and prior with no confirmed fix. Check the upstream issue and limit untrusted input.

Safeguard Security Team
3 min read

CVE-2020-26304 is a high severity (CVSS 7.5) regular expression denial of service flaw in Foundation, the front end framework. Versions 6.3.3 and prior contain vulnerable expressions. The record said it was unknown whether a fix existed, so check the project's issue 12180 before relying on any version.

What's affected

  • Foundation (foundation-sites) 6.3.3 and prior, per the record.
  • Fixed: not stated. GitHub Security Lab says three url related expressions were flagged and names no fix.

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 foundation-sites 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. Search for foundation-sites in your lockfiles and bundled assets.
  2. Check the upstream issue for fix status.
  3. Where the validation code is used, avoid pre-filling inputs from untrusted sources.
  4. Plan an upgrade to a release that addresses the issue once one is confirmed.

After you patch, record the new version for Foundation 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. Here the advisory notes that if a server pre-fills an input the attacker controls, the victim's browser could crash, so the impact is on the client.

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

Is this a server or browser problem?

The advisory says a browser could crash if a server pre-fills an input the attacker controls, so the main impact is in the browser.

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