CVE-2026-96628
Arcane: Environment access token bypasses the admin-required authorization gate on
Published Oct 16, 2026 · corrected/updated Oct 16, 2026 · evidence confidence medium
## Summary Arcane v2.10.2 contains an authorization inconsistency in . When a request supplies a valid environment access token through the header, resolves the associated environment, installs an environment-scoped permission set, and immediately calls . This occurs before the middleware evaluates the option and verifies that the caller is a global administrator. As a result, an environment-scoped access token can access routes protected with , despite the corresponding intentionally containing no global or sudo permissions. In v2.10.2, the affected admin-only surface is the manager's Go diagnostic interface under: This exposes diagnostic and runtime profiling information that the application explicitly intends to restrict to global administrators. The issue is an incorrect authorization vulnerability (CWE-863). ## Details ### 1. Environment access tokens are accepted by the manager authentication middleware The production authentication middleware is configured with an environment access-token resolver: Conceptually, the middleware is constructed as: Therefore, the authentication path is active in the production manager. ### 2. The environment-token path returns before authorization options are evaluated The relevant logic is in: first checks the header. When the token resolves to an environment, the middleware installs an environment-scoped permission set and immediately continues processing: The important part is the unconditional: The normal authentication path later evaluates the middleware's option: The environment-token branch never reaches this check. Consequently, has no effect when authentication succeeds through a valid environment access token. This creates an authorization inconsistency between authentication mechanisms: - normal user/session authentication → is enforced; - environment access-token authentication → is bypassed. ### 3. Environment tokens are intentionally not global-administrator credentials defines the effective permissions assigned to
Grounded briefings
Catalog interpretations for three audiences. Each brief cites ingested metadata and the original advisories below. They are not independent research and they do not invent exploit steps.
Executive
CVE-2026-96628 is a medium public vulnerability record for this product. It is not currently listed in the CISA Known Exploited catalog. Check the linked vendor or CERT advisories for patch status. This summary is a catalog interpretation of the ingested metadata and cites the original advisories below.
System administrator
Identify whether this product is in your estate, then compare installed versions with the affected ranges. Affected packages or ranges on record: github.com/getarcaneapp/arcane/backend/v2 (0 → 2.11.0). Check the linked vendor or CERT advisories for patch status. Prefer the vendor or distribution advisory linked in Sources before changing production systems. This is a catalog interpretation, not a runbook.
Security analyst
Signals on file: CVSS 4.3. It is not currently listed in the CISA Known Exploited catalog. Weakness classes: CWE-863. Sources contributing to this record: github, osv. Public exploit references, when present, are outbound links only and are not proof of active exploitation. This is a catalog interpretation of stored metadata.
Exploitation and remediation
Exploitation evidence
Not listed as known exploited in CISA KEV. Not in the CISA KEV catalog.
Patch and remediation
No required-action text is stored yet. Use the vendor or CERT links in Sources for patch availability.
Safe detection guidance
Compare installed versions with the affected ranges below and verify the advisory from the original publisher. This site stores metadata and outbound links only; it does not ship exploit code or proof-of-concept payloads.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 16, 2026 · GitHub Advisory Database
Detected
## Summary Arcane v2.10.2 contains an authorization inconsistency in . When a request supplies a valid environment access token through the header, resolves the associated environment, installs an environment-scoped permission set, and immediately calls . This occurs before the middleware evaluates the option and verifies that the caller is a global administrator. As a result, an environment-scope
Oct 16, 2026 · GitHub Advisory Database
Fix available
github.com/getarcaneapp/arcane/backend/v2 fixed in 2.11.0
Oct 16, 2026 · GitHub Advisory Database
Fix available
github.com/getarcaneapp/arcane/backend/v2 fixed in 2.11.0
Oct 16, 2026 · GitHub Advisory Database
Updated
## Summary Arcane v2.10.2 contains an authorization inconsistency in . When a request supplies a valid environment access token through the header, resolves the associated environment, installs an environment-scoped permission set, and immediately calls . This occurs before the middleware evaluates the option and verifies that the caller is a global administrator. As a result, an environment-scope
Affected
- Go github.com/getarcaneapp/arcane/backend/v20 → 2.11.0
Sources
- GitHub Advisory DatabasePackage advisoryGHSA-mp22-58ff-6fhr
GitHub Advisory Database record mirrored by OSV.
github.com - OSV.devPackage advisoryGHSA-mp22-58ff-6fhr
Arcane: Environment access token bypasses the admin-required authorization gate on
osv.dev