# CVE-2026-45627: Arcane: Unauthenticated reflected XSS via SVG color parameter in /api/app-images/logo enables admin account takeover

> Unauthenticated reflected XSS in Arcane allows attackers to execute JavaScript and hijack admin accounts via a crafted URL.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N`)
- **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:** Yes
- **Published:** 29 May 2026
- **Updated:** 29 May 2026
- **Also known as:** GHSA-q2pj-8v84-9mh5, GO-2026-5561

## What is CVE-2026-45627?

CVE-2026-45627 is a high-severity cross-site scripting vulnerability in getarcaneapp arcane, published on 29 May 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

Arcane is an interface for managing Docker containers, images, networks, and volumes. Prior to 1.19.0, the unauthenticated GET /api/app-images/logo endpoint reflects a user-supplied color query parameter into the body of an SVG document via strings.ReplaceAll with no escaping. The substitution lands inside a <style> element of the embedded logo.svg, allowing an attacker to close the style block and inject executable <script> content. Because the response is served as image/svg+xml and Arcane sets no Content-Security-Policy or X-Content-Type-Options headers, navigating a logged-in admin victim to a crafted URL executes attacker-controlled JavaScript in Arcane's origin and rides the victim's HttpOnly JWT cookie to fully compromise the admin account. This vulnerability is fixed in 1.19.0.

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

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

3 open source packages ship an affected version, including github.com/getarcaneapp/arcane/backend.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/getarcaneapp/arcane/backend` | Go | All versions | 1.19.0 |
| `github.com/getarcaneapp/arcane/backend` | Go | All versions | 1.19.0 |
| `github.com/getarcaneapp/arcane/backend` | Go | All versions | 1.19.0 |

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

Upgrade github.com/getarcaneapp/arcane/backend to 1.19.0 or later.

## Is CVE-2026-45627 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45627 is a high-severity cross-site scripting vulnerability in getarcaneapp arcane, published on 29 May 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: There is no known exploitation of CVE-2026-45627 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/getarcaneapp/arcane/backend (Go): affected all versions; fixed in 1.19.0
- github.com/getarcaneapp/arcane/backend (Go): affected all versions; fixed in 1.19.0
- github.com/getarcaneapp/arcane/backend (Go): affected all versions; fixed in 1.19.0

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

## Sources

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

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