# CVE-2026-121445: svg-sanitizer 1.0.0 before 1.1.0 ReDoS and Fail-Open via image-set CSS Stripping


- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Nov 2026
- **Updated:** 3 Nov 2026
- **Also known as:** GHSA-4rvh-48q4-5726, GHSA-94x8-pw3c-6qcq

## What is CVE-2026-121445?

CVE-2026-121445 is a high-severity vulnerability in darylldoyle svg-sanitizer, published on 3 Nov 2026. 

### Official description

darylldoyle svg-sanitizer from 1.0.0 before 1.1.0 contains a regular expression denial of service vulnerability in the image-set pattern of stripRemoteCssTokens() when removeRemoteReferences is enabled. Attackers can submit SVGs with many unclosed image-set tokens to exhaust CPU, or trigger PCRE limits causing sanitize() to throw a TypeError and leave unsanitized content.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

## Which versions are affected by CVE-2026-121445?


## How do I fix CVE-2026-121445?

No fix has been published for CVE-2026-121445 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-121445 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121445 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-121445 and fix it if it is affected.

What it is: CVE-2026-121445 is a high-severity vulnerability in darylldoyle svg-sanitizer, published on 3 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121445 exists.

Affected product: darylldoyle svg-sanitizer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-121445/ (Markdown: https://insights.sbomify.com/CVE-2026-121445/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-121445
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-121445
- OSV: https://osv.dev/vulnerability/CVE-2026-121445

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-121445/
Summaries are generated and may contain mistakes; the official description above is the record.
