Authorization Flaw in github.com/getarcaneapp/arcane/backend/v2 (CVE-2026-96628)
Summary
Vulnerability in github.com/getarcaneapp/arcane/backend/v2 (CVE-2026-96628). Risk of unauthorized operations or information disclosure. Exploitable via GET /api/debug/pprof/heap. Mitigation: upgrade to 2.11.0 or later.
Original description
The description as published by the source.
Summary
Arcane v2.10.2 contains an authorization inconsistency in AuthMiddleware.managerAuth.
When a request supplies a valid environment access token through the X-Arcane-Agent-Token header, managerAuth resolves the associated environment, installs an environment-scoped permission set, and immediately calls next(c).
This occurs before the middleware evaluates the AdminRequired option and verifies that the caller is a global administrator.
As a result, an environment-scoped access token can access routes protected with WithAdminRequired(), despite the corresponding EnvironmentPermissionSet intentionally containing no global or sudo permissions.
In v2.10.2, the affected admin-only surface is the manager's Go pprof diagnostic interface under:
/api/debug/pprof/*
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:
backend/internal/di/providers.go
Conceptually, the middleware is constructed as:
auth.NewAuthMiddleware(authService, cfg).
WithApiKeyValidator(apiKey).
WithEnvironmentAccessTokenResolver(env).
WithPermissionResolver(role)
Therefore, the X-Arcane-Agent-Token authenticatio…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-96628 has been found in github.com/getarcaneapp/arcane/backend/v2.
Attackers can target a specific entry point like GET /api/debug/pprof/heap over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade github.com/getarcaneapp/arcane/backend/v2 to 2.11.0 or later.
If unsure, ask your IT team or search "github.com/getarcaneapp/arcane/backend/v2 CVE-2026-96628" on the vendor's site.
CVE-2026-96628 (github.com/getarcaneapp/arcane/backend/v2) — CWE-863 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/debug/pprof/heap / AuthMiddleware.managerAuth / managerAuth / AdminRequired
Patched: 2.11.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Incorrect authorization (CWE-863) exists in github.com/getarcaneapp/arcane/backend/v2. Attackers reach the vulnerable code path via GET /api/debug/pprof/heap.
Check the vendor advisory for the affected versions of github.com/getarcaneapp/arcane/backend/v2. Attack surface: GET /api/debug/pprof/heap / AuthMiddleware.managerAuth / managerAuth / AdminRequired.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 2.11.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /api/debug/pprof/heap requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/getarcaneapp/arcane/backend/v2' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/getarcaneapp/arcane/backend/v2' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/getarcaneapp/arcane/backend/v2を grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /api/debug/pprof/heap' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/debug/pprof/heapへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade github.com/getarcaneapp/arcane/backend/v2 to 2.11.0ステージング環境で 2.11.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /api/debug/pprof/heap on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。