# CVE-2026-117539: darylldoyle svg-sanitizer before 1.0.0 CSS Injection and Remote Reference Bypass


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:N/VA:N/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-crrh-v25v-h623, GHSA-qhmf-972w-m957

## What is CVE-2026-117539?

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

### Official description

darylldoyle svg-sanitizer before 1.0.0 contains CSS injection and remote reference bypass vulnerabilities that allow attackers to embed external resources by uploading crafted SVG files. Attackers can use unsanitized style content, unquoted url() values, or image href attributes to exfiltrate page data, track users, or disclose visitor IP addresses.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-117539 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-117539 is a medium-severity vulnerability in darylldoyle svg-sanitizer, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-117539 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-117539/ (Markdown: https://insights.sbomify.com/CVE-2026-117539/index.md)
```

## Sources

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

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