CVE-2026-42461
- Source
- https://cve.org/CVERecord?id=CVE-2026-42461
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-42461.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-42461
- Aliases
- Downstream
- Related
- Published
- 2026-05-09T03:30:13.371Z
- Modified
- 2026-08-05T03:32:16.239812163Z
- Severity
-
- 8.7 (High) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N CVSS Calculator
- Summary
- Arcane Vulnerable to Unauthenticated Disclosure of Custom Compose Template Content (incl. `.env` secrets)
- Details
-
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.
- Database specific
{ "unresolved_ranges": [ { "extracted_events": [ { "fixed": "1.18.0" } ], "source": "AFFECTED_FIELD" } ], "cwe_ids": [ "CWE-862" ], "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/42xxx/CVE-2026-42461.json", "cna_assigner": "GitHub_M" }- References