CVE-2026-86114: Arcane before 2.0.0 Missing Administrator Authorization on the Compose Template Mutation Endpoints

Published Sep 5, 2026
·
Updated

Arcane versions before 2.0.0 fail to properly restrict template operations, allowing default user role accounts to create, modify, and delete compose templates including instance-wide defaults. Attackers can inject malicious container configurations with privileged settings or host path mounts that execute with administrative privileges when deployed by administrators.

Affected Software

1 affected component
Arcane Arcane<2.0.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Arcane to a version that resolves this vulnerability.

    Fixed in 2.0.0
  2. Compensating control

    Restrict access to the Arcane Compose Template Mutation Endpoints so only administrators can create, modify, or delete compose templates.

Event History

Sep 5, 2026
CVE Published
via MITRE·09:59 AM
Data Sourced
via MITRE·09:59 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:16 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An account with the default user role can exploit it. The attacker does not need administrator authorization, but must be able to access the compose template mutation endpoints.

2

What is the practical impact of a successful exploit?

A low-privileged user can create, modify, or delete compose templates, including instance-wide default templates. They can inject privileged container settings or host path mounts that may execute with administrative privileges when an administrator deploys the affected template.

3

Are default configurations affected?

Yes. The issue specifically affects default user role accounts and includes the ability to alter instance-wide default compose templates.

4

What should be done if immediate upgrading is not possible?

Restrict access to the compose template mutation endpoints so default user role accounts cannot create, modify, or delete templates. Review templates, especially instance-wide defaults, for unexpected privileged settings or host path mounts before administrators deploy them.

5

How can administrators identify possible prior abuse?

Review compose templates and instance-wide default templates for unauthorized changes, particularly privileged container configurations and host path mounts. Check whether templates were created, modified, or deleted by accounts assigned the default user role.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203