# CVE-2026-105708: imgproxy SVG svg.go sanitizeElement cross site scripting

> Remote attackers can execute cross-site scripting attacks via malicious SVG files processed by imgproxy, potentially compromising user sessions.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-5qgf-cr4x-pc9r

## What is CVE-2026-105708?

CVE-2026-105708 is a medium-severity cross-site scripting vulnerability in imgproxy, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A flaw has been found in imgproxy up to 4.0.17. Affected by this vulnerability is the function sanitizeElement of the file processing/svg/svg.go of the component SVG Handler. Executing a manipulation can lead to cross site scripting. It is possible to launch the attack remotely. The exploit has been published and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-105708 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105708 is a medium-severity cross-site scripting vulnerability in imgproxy, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-105708 exists.

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

## Sources

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

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