CVE-2026-42461: getarcaneapp arcane · Missing Authorization
Affects getarcaneapp arcaneSource CVE Database V5
Not known to be exploited · public detection template (Nuclei) · CVSS 8.7 High : upgrade to 1.18.0 soon.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 1.2% chance of exploitation in 30 days – higher than 70% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.18.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 9 May 2026
Detectable: evidence found.
nuclei template: Arcane < 1.18.0 - Unauthenticated Template and Env Disclosure
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade arcane and getarcaneapp/arcane to 1.18.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| getarcaneapparcane | Affected
| Fixed in
|
GitHubgetarcaneapp/arcanepkg:github/getarcaneapp/arcaneOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Arcane to version 1.18.0 or later, where this missing authorization vulnerability is patched. Until then, restrict network access to the vulnerable endpoints to trusted users only. Patch status is not explicitly stated but the vendor has released version 1.18.0 containing the fix, so upgrading is the recommended remediation.
Description
Arcane is an interface for managing Docker containers, images, networks, and volumes. Prior to version 1.18.0, four GET endpoints under /api/templates* in Arcane's Huma backend are registered without any Security requirement, allowing any unauthenticated network client to list and read the full Compose YAML and .env content of every custom template stored in the instance. Because Arcane's UI exposes a "Save as Template" flow on the project / swarm-stack creation pages that persists the operator's real env content (database passwords, API keys, etc.) verbatim, this missing authorization is an unauthenticated read of operator secrets in practice — not a theoretical info-disclosure. The frontend explicitly treats /customize/templates/* as an authenticated area (PROTECTED_PREFIXES in frontend/src/lib/utils/redirect.util.ts), and every CRUD operation (POST/PUT/DELETE) on the same paths requires a Bearer/API key, so this is a clear backend authorization gap, not intended public access. This issue has been patched in version 1.18.0.