← Back
CVE-2026-55678
Vulnerability in github.com/basekick-labs/arc (CVE-2026-55678)
Summary
vulnerability in github.com/basekick-labs/arc (CVE-2026-55678). Risk of unauthorized operations or information disclosure. Exploitable via ``cluster.shared_secret``. Mitigation: upgrade to `0.0.0-20260615160325-38402ad2ebdd` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-55678** has been found in github.com/basekick-labs/arc.
Attackers can target a specific entry point like ``cluster.shared_secret`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade github.com/basekick-labs/arc to **0.0.0-20260615160325-38402ad2ebdd** or later.
If unsure, ask your IT team or search "github.com/basekick-labs/arc CVE-2026-55678" on the vendor's site.
CVE-2026-55678 (github.com/basekick-labs/arc) — CWE-284 /
Attack surface: `cluster.shared_secret` / `cluster.replication_enabled` / `JoinRequest` / `node_id`
Patched: `0.0.0-20260615160325-38402ad2ebdd` — 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.
❓ What is the problem
**A vulnerability** (CWE-284) exists in github.com/basekick-labs/arc. Attackers reach the vulnerable code path via ``cluster.shared_secret`` without authentication.
📍 Affected scope
github.com/basekick-labs/arc — . Attack surface: `cluster.shared_secret` / `cluster.replication_enabled` / `JoinRequest` / `node_id`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.0.0-20260615160325-38402ad2ebdd**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'github.com/basekick-labs/arc' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/basekick-labs/arc' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/basekick-labs/arc` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/basekick-labs/arc to 0.0.0-20260615160325-38402ad2ebddステージング環境で 0.0.0-20260615160325-38402ad2ebdd に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/basekick-labs/arc
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.0-20260615160325-38402ad2ebdd"}]}]