# CVE-2026-117541: svg-sanitizer 0.11.0 before 1.1.0 Uncaught LogicException DoS via sanitize()


- **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:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-82gx-99vw-x254, GHSA-cgcm-4g72-hfgw

## What is CVE-2026-117541?

CVE-2026-117541 is a medium-severity vulnerability in darylldoyle svg-sanitizer, published on 27 Oct 2026. 

### Official description

svg-sanitizer from 0.11.0 before 1.1.0 contains an uncaught exception vulnerability that allows attackers to crash callers by submitting well-formed XML without a top-level svg root. Attackers can supply documents with a non-svg root or nested svg element, causing Sanitizer::sanitize() to throw a LogicException instead of returning false, crashing workers or bypassing upload rejection.

Weakness: CWE-248 (Uncaught Exception)

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


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

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

## Is CVE-2026-117541 being exploited?

There is no known exploitation of CVE-2026-117541 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-117541 is a medium-severity vulnerability in darylldoyle svg-sanitizer, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-117541 in the wild and no public exploit code.

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-117541/ (Markdown: https://insights.sbomify.com/CVE-2026-117541/index.md)
```

## Sources

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

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