CVE-2026-45627
Received Received - Intake
Stored XSS in Arcane Docker Management Interface via SVG Logo Injection

Publication date: 2026-05-29

Last updated on: 2026-05-29

Assigner: GitHub, Inc.

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-29
Last Modified
2026-05-29
Generated
2026-05-29
AI Q&A
2026-05-29
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
getarcaneapp arcane to 1.19.0 (exc)
getarcaneapp arcane to 1.18.1 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2026-45627 is a high-severity reflected Cross-Site Scripting (XSS) vulnerability in the Arcane application (versions up to 1.18.1). It occurs because the application reflects a user-supplied 'color' query parameter into an SVG document without proper escaping. This allows an attacker to close the existing <style> block and inject malicious <script> content inside the SVG.

Since the response is served as image/svg+xml and Arcane does not set security headers like Content-Security-Policy or X-Content-Type-Options, an attacker can craft a URL that, when visited by a logged-in admin, executes attacker-controlled JavaScript in Arcane's origin.

This script execution can hijack the victim's HttpOnly JWT cookie, leading to full compromise of the admin account.


How can this vulnerability impact me? :

This vulnerability allows an attacker to fully compromise an admin account in the Arcane application by executing arbitrary JavaScript in the context of the application.

  • The attacker can hijack the admin's session via the HttpOnly JWT cookie.
  • They can create persistent admin accounts.
  • They gain access to sensitive secrets.
  • They can control Docker containers, registries, and GitOps repositories managed by Arcane.

The attack requires minimal user interaction, only that the victim clicks a crafted link.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by testing the `/api/app-images/logo` endpoint for reflected Cross-Site Scripting (XSS) via the `color` query parameter. Specifically, sending crafted requests with malicious payloads in the `color` parameter and observing if the response SVG document reflects the input without proper escaping indicates the presence of the vulnerability.

A simple detection method is to use curl or similar HTTP clients to send a request with a payload that attempts to break out of the style block and inject script tags. For example:

  • curl -i "http://<arcane-host>/api/app-images/logo?color=%3C%2Fstyle%3E%3Cscript%3Ealert(1)%3C%2Fscript%3E"

If the response contains the injected `<script>alert(1)</script>` inside the SVG, the vulnerability is present.


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include upgrading the Arcane application to version 1.19.0 or later, where this vulnerability is fixed.

Additional mitigations involve adding security headers such as Content-Security-Policy and X-Content-Type-Options to prevent execution of injected scripts.

Validating and sanitizing user input on the `color` query parameter to prevent injection of malicious content is also recommended.

Serving images from a separate origin can help isolate the SVG content and reduce the impact of such attacks.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

This vulnerability allows an attacker to fully compromise an admin account by executing malicious JavaScript in the context of the application, leading to session hijacking and unauthorized access to sensitive data and control over Docker containers and related resources.

Such unauthorized access and potential data breaches can lead to non-compliance with common standards and regulations like GDPR and HIPAA, which require protection of sensitive data and strict access controls.

Failure to implement proper input validation, security headers, and isolation of content as described in the vulnerability increases the risk of violating these regulations due to exposure of personal or sensitive information.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart