Sign in Sign up
JA · EN · FR
SecPulse
Categories
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.

Original description

The description as published by the source.

Summary

Arc Enterprise clustering accepts cluster join requests without authentication when cluster.enabled=true but cluster.shared_secret is not configured. The coordinator validates HMAC authentication only if a shared secret is non-empty; otherwise, a network attacker who can reach the coordinator port can send a join request with attacker-controlled node addresses and role. Accepted nodes are marked healthy, registered locally or added as Raft voters, and can be selected by the
cluster router for forwarded authenticated requests.

Details

Cluster defaults include an empty shared secret and TLS disabled:

  • internal/config/config.go:943-950 defaults cluster.enabled=false, cluster.cluster_name="arc-cluster", and cluster.coordinator_addr=":9100".
  • internal/config/config.go:1001-1005 defaults cluster.shared_secret="" and cluster.tls_enabled=false.

Startup requires a shared secret only for file replication, not for all clustering/join/routing use:

  • cmd/arc/main.go:1258-1265 hard-fails without cluster.shared_secret only when cluster.replication_enabled is true.

The join request contains attacker-supplied node identity, role, and addresses:

  • internal/cluster/protocol/messages.go:127-142 defines JoinRequest fields including node_id, role, raft_addr, api_addr, coord_addr, plus optional auth fields.

The coordinator validates HMAC only when the configured shared secret is non-empty:

  • internal/cluster/coordinator.go:1066-1081…

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-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.
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.

📍 Affected scope

Check the vendor advisory for the affected versions of 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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify 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 し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/basekick-labs/arc to 0.0.0-20260615160325-38402ad2ebdd

    ステージング環境で 0.0.0-20260615160325-38402ad2ebdd に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/basekick-labs/arc
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.0.0-20260615160325-38402ad2ebdd"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details