# CVE-2026-121443: svg-sanitizer from 1.1.0 before 1.1.1 Denial of Service via Unclosed Tag


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-8888-g577-32c9, GHSA-f7cw-vfxq-7ph2

## What is CVE-2026-121443?

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

### Official description

svg-sanitizer from 1.1.0 before 1.1.1 contains a denial of service vulnerability that allows remote attackers to crash requests by submitting SVG input ending inside an unclosed tag. Attackers can upload truncated input like a single '<' to trigger an uncaught ValueError from strpos() in hasElementWithTooManyAttributes() or hasInternalDtdSubset() on PHP 8, failing the request.

Weakness: CWE-248 (Uncaught Exception)

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


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

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

## Is CVE-2026-121443 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-121443 is a medium-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-121443 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-121443/ (Markdown: https://insights.sbomify.com/CVE-2026-121443/index.md)
```

## Sources

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

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