Quick answers
- Is CVE-2026-45627 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45627 being exploited in the wild.
- How severe is CVE-2026-45627?
- High severity, with a CVSS score of 8.2, published 29 May 2026.
- Which products and versions are affected?
- github.com/getarcaneapp/arcane/backend (Go) <= 1.18.1, SEMVER:introduced=0,fixed=1.19.0.
- Is there a fix for CVE-2026-45627?
- Yes. github.com/getarcaneapp/arcane/backend (Go): upgrade to 1.19.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-45627 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-45627?
- Check whether you run github.com/getarcaneapp/arcane/backend (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- github.com/getarcaneapp/arcane/backend (Go): upgrade to 1.19.0 or later
go get github.com/getarcaneapp/arcane/backend@v1.19.0
Technical details
A reflected Cross-Site Scripting (XSS) vulnerability exists in the `/api/app-images/logo` endpoint of Arcane due to improper neutralization of the `color` query parameter. The application uses `strings.ReplaceAll` to inject the user-supplied string directly into a `<style>` block within an SVG document. An attacker can break out of the style block and inject a `<script>` element. Because the application lacks a Content Security Policy (CSP) and `X-Content-Type-Options: nosniff`, browsers will execute the script if a victim navigates to the crafted URL. This allows for session riding against authenticated users; an attacker can bypass HttpOnly cookie protections by making same-origin API requests (such as creating a new admin user) via the victim's browser. The issue is fixed in version 1.19.0.
Affected products
- getarcaneapp Arcane <= 1.18.1
Identifiers
- CVE-2026-45627
- GHSA-q2pj-8v84-9mh5
- GO-2026-5561
Timeline
- 2026-05-11: advisory: Vendor advisory published on GitHub
- 2026-05-29: disclosed: CVE published to NVD