Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-63406 medium CVSS 5.9

Vulnerability in github.com/anycable/anycable (CVE-2026-63406)

Summary

Vulnerability in github.com/anycable/anycable (CVE-2026-63406). Confidential information can be exposed externally. Exploitable via telemetry.anycable.io. Mitigation: upgrade to 1.6.15 or later.

Original description

The description as published by the source.

Summary

The telemetry subsystem embeds a hardcoded auth token ("secret") in the public source and transmits raw CLI arguments—including --secret, --jwt_secret, and --http_rpc_secret values—to a third-party telemetry endpoint.

Details

In telemetry/config.go line 12, var authToken = "secret" is committed in the public repository and used to authenticate to https://telemetry.anycable.io. In telemetry/telemetry.go, clusterFingerprint() (line 320) calls both anycableFileConfig(c.ConfigFilePath) (line 333), which reads the full TOML config file contents, and anycableCLIArgs() (line 402), which reads os.Args[1:] verbatim—including any --secret=..., --jwt_secret=..., --http_rpc_secret=... arguments. Both raw values are passed to generateDigest() (line 373), meaning the actual secret strings flow through the code path and are included in telemetry data sent to the third-party server. Since the hardcoded authToken = "secret" is public, any attacker who can perform DNS hijacking or is positioned on the network path can intercept and read the telemetry payload containing operator credentials.

PoC

  1. Read telemetry/config.go in the public repo to find authToken = "secret".
  2. Set up a DNS spoof for telemetry.anycable.io pointing to an attacker-controlled server.
  3. Start anycable-go with --secret=my-production-secret.
  4. The server sends a POST to the attacker's endpoint with the telemetry JSON payload. The clusterFingerprint field…

Source: NIST National Vulnerability Database 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-63406 has been found in github.com/anycable/anycable.
Attackers can target a specific entry point like telemetry.anycable.io over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.9/10.
What to do: upgrade github.com/anycable/anycable to 1.6.15 or later.
If unsure, ask your IT team or search "github.com/anycable/anycable CVE-2026-63406" on the vendor's site.

CVE-2026-63406 (github.com/anycable/anycable) — CWE-312 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: telemetry.anycable.io / clusterFingerprint / os.Args / authToken
Patched: 1.6.15 — 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-312) exists in github.com/anycable/anycable. Attackers reach the vulnerable code path via telemetry.anycable.io without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/anycable/anycable. Attack surface: telemetry.anycable.io / clusterFingerprint / os.Args / authToken.

🔥 Severity

Severity: Medium (CVSS 5.9/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 1.6.15.

🛡️ 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/anycable/anycable' . 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/anycable/anycable' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/anycable/anycable を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/anycable/anycable to 1.6.15

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

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

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

Affected packages

go github.com/anycable/anycable
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.6.15"}]}]

References

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