dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-45627

HIGH · 8.2 CVSS v3.1 Published 2026-05-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Arcane Docker management interface suffers from a stored XSS in the GET /api/app-images/logo endpoint. The color query parameter is reflected into an SVG document via strings.ReplaceAll without escaping, allowing injection of closing style tags and executable script content. Since the response is served as image/svg+xml without CSP or X-Content-Type-Options headers, a logged-in admin visiting a crafted URL enables attacker-controlled JavaScript execution in Arcane's origin, exfiltrating the HttpOnly JWT cookie for full admin account compromise.

MitigationUpgrade to Arcane 1.19.0 or later, which implements proper escaping of user-supplied parameters before insertion into SVG content.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Arcane installation and version
    Locate the Arcane installation (common paths: /opt/arcane, /usr/local/arcane, or check docker ps for arcane container). Run 'arcane --version' or inspect the container/image version tag. Compare the version number to the affected range (versions prior to 1.19.0).
    Affected if Arcane version is installed and is lower than 1.19.0
  2. Verify the vulnerable endpoint exists
    Make a GET request to /api/app-images/logo?color=test and verify the endpoint responds with SVG content (Content-Type: image/svg+xml). Example: curl -s -o /dev/null -w '%{content_type}' http://localhost:PORT/api/app-images/logo?color=test
    Affected if The endpoint responds with SVG content and accepts the color query parameter
  3. Check for missing security headers in response
    Inspect the HTTP response headers from the /api/app-images/logo endpoint. Look for absence of 'Content-Security-Policy' and 'X-Content-Type-Options' headers. Example: curl -I http://localhost:PORT/api/app-images/logo?color=test
    Affected if Response lacks CSP and X-Content-Type-Options: nosniff headers, making script execution possible
  4. Confirm color parameter reflection without escaping
    Send a test payload in the color parameter such as 'test</style><script>alert(1)</script>' and examine if the raw injected tags appear in the response body unescaped. Example: curl 'http://localhost:PORT/api/app-images/logo?color=test</style><script>alert(1)</script>'
    Affected if The injected style and script tags appear literally in the SVG response without HTML entity encoding

User is affected if running Arcane Docker management interface version lower than 1.19.0 with the /api/app-images/logo endpoint accessible and missing security headers on SVG responses.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Arcane 1.19.0 or later, which implements proper escaping of user-supplied parameters before insertion into SVG content.

Recommended fix High confidence

Arcane version 1.19.0

  1. Upgrade Arcane to version 1.19.0 or later to remediate the XSS vulnerability
  2. After upgrading, verify that the /api/app-images/logo endpoint with a malicious color parameter no longer executes arbitrary JavaScript
  3. Confirm that the response now properly escapes or does not reflect user-supplied input into the SVG style element

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45627 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45627 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data