CVE-2026-121707: Effect: ReDoS in Schema.TemplateLiteral compiled regex
High
- OSV id
- GHSA-7589-6fvf-x4pw
- Also known as
- CVE-2026-121707
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| effect npm |
< 3.22.1 | 3.22.1 |
How to fix it
Upgrade effect to 3.22.1 or later.
npm install effect@3.22.1
# if it is an indirect dependency: npm update effect (or npm audit fix)
- If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
- Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
Not sure whether your project uses an affected version? Check your lockfile below for free.
Details
Impact
Schema.TemplateLiteral compiles each Schema.String span to the lazy wildcard [\s\S]*? and decodes input by running the resulting regular expression against it. When a template has two or more Schema.String spans, for example:
Schema.TemplateLiteral(Schema.String, ":", Schema.String, ":", Schema.String, "X")
the regex contains several ambiguous wildcards. A non-matching input makes the backtracking engine try combinations across all of them, so matching time grows cubically with input length. A 5,000-character string of : characters blocks the event loop for about 15 seconds.
Applications that decode untrusted input with such a schema are affected. That includes Schema.decodeUnknown, Schema.decodeUnknownSync and Schema.is, and anything built on them, such as HttpApi request payloads and @effect/rpc payloads.
Patches
Fixed in effect@3.22.1 (#6761). Template literals whose spans are all Schema.String are now matched with a linear left-to-right scan instead of a regular expression.
Workarounds
If you can't upgrade, check the input length before the template literal runs. Adding Schema.maxLength with .pipe doesn't help, because the filter runs after the regex. Put the length check on the input side instead:
Schema.compose(Schema.String.pipe(Schema.maxLength(256)), MyTemplateLiteral)
Rejecting oversized request bodies before they reach the schema also works.
References
- GHSA-7589-6fvf-x4pw on OSV.dev
- Web: https://github.com/Effect-TS/effect/security/advisories/GHSA-7589-6fvf-x4pw
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-121707
- Web: https://github.com/Effect-TS/effect/pull/6761
- Web: https://github.com/Effect-TS/effect/commit/3cc3c6e1a64cbdc360e9d28e44f3ec3ce0ece6e3
- Package: https://github.com/Effect-TS/effect
- Web: https://github.com/Effect-TS/effect/releases/tag/effect@3.22.1
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.