CVE-2026-63406: AnyCable Telemetry Subsystem Contains Hardcoded Authentication Vulnerability

MODERATE
Advisory Identifier: GHSA-w72w-9qmj-c9qm
CVSS 5.9
CWE-312 CWE-798
Published
Advisory Summary

CVE-2026-63406 is a MODERATE (CVSS 5.9) telemetry subsystem contains hardcoded authentication vulnerability (CWE-312: Cleartext Storage of Sensitive Information) affecting AnyCable libraries in the Go ecosystem. The issue involves telemetry subsystem contains hardcoded authentication token and transmits cli arguments including secrets. Remediation is available by upgrading affected packages to version 1.6.15.

CVE-2026-63406 at a Glance

CVE Identifier CVE-2026-63406
GHSA Identifier GHSA-w72w-9qmj-c9qm
Severity MODERATE
CVSS v3.1 Base Score 5.9
CWE Classification CWE-312: Cleartext Storage of Sensitive Information
Affected Product AnyCable
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 5.9

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-63406

To remediate this vulnerability, upgrade all affected AnyCable dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/anycable/anycable fixed: 1.6.15
Upgrade github.com/anycable/anycable to 1.6.15
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/anycable/anycable

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-63406, inspect your project dependencies for AnyCable:

inspect dependencies for github.com/anycable/anycable

Analyze the terminal output to locate any version of AnyCable in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.6.15), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-312: Cleartext Storage of Sensitive Information, where the product stores sensitive information in cleartext within a resource that might be accessible to another control sphere. In AnyCable, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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 contains data derived from raw `os.Args` including `--secret=my-production-secret`. ### Impact In MITM/DNS-hijack scenarios, production secrets (JWT secrets, broadcast keys, RPC auth) are exposed to third parties. The hardcoded `authToken = "secret"` provides no protection since it is known to anyone reading the open-source code. ### Fix 1. Remove the hardcoded `authToken` from source; generate or require operator configuration at build time or deployment time. 2. Remove `anycableCLIArgs()` from the fingerprint computation, or sanitize it to exclude values of secret-bearing flags before hashing. 3. Add a documented opt-out mechanism for telemetry.

CVE-2026-63406 Affected AnyCable Versions

1 component(s)
Fixed Versions:
1.6.15
Product / Package Ecosystem Affected Versions Fixed Version
github.com/anycable/anycable
Go
< 1.6.15
1.6.15

References

Frequently Asked Questions

What is CVE-2026-63406?
CVE-2026-63406 is a security vulnerability in AnyCable involving Telemetry Subsystem Contains Hardcoded Authentication Token and Transmits CLI Arguments Including Secrets under CWE-312: Cleartext Storage of Sensitive Information.
Which AnyCable versions are affected?
Affected versions include releases prior to 1.6.15 across affected packages: github.com/anycable/anycable.
What version fixes CVE-2026-63406?
Upgrading to 1.6.15 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/anycable/anycable affected?
Yes, github.com/anycable/anycable is affected in releases prior to 1.6.15. Upgrade your dependency to 1.6.15 or later.
What is the CVSS score of CVE-2026-63406?
CVE-2026-63406 has a CVSS v3.1 base score of 5.9 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-63406?
CVE-2026-63406 is classified under CWE-312: Cleartext Storage of Sensitive Information (The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.).
How can I check Go dependencies for CVE-2026-63406?
Run the dependency tree command: 'inspect dependencies for github.com/anycable/anycable'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-w72w-9qmj-c9qm",
  "modified" : "2026-09-18T17:17:29Z",
  "published" : "2026-09-18T17:17:29Z",
  "aliases" : [ "CVE-2026-63406" ],
  "summary" : "AnyCable: Telemetry Subsystem Contains Hardcoded Authentication Token and Transmits CLI Arguments Including Secrets",
  "details" : "### Summary\nThe 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.\n\n### Details\nIn `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.\n\n### PoC\n1. Read `telemetry/config.go` in the public repo to find `authToken = \"secret\"`.\n2. Set up a DNS spoof for `telemetry.anycable.io` pointing to an attacker-controlled server.\n3. Start anycable-go with `--secret=my-production-secret`.\n4. The server sends a POST to the attacker's endpoint with the telemetry JSON payload. The `clusterFingerprint` field contains data derived from raw `os.Args` including `--secret=my-production-secret`.\n\n### Impact\nIn MITM/DNS-hijack scenarios, production secrets (JWT secrets, broadcast keys, RPC auth) are exposed to third parties. The hardcoded `authToken = \"secret\"` provides no protection since it is known to anyone reading the open-source code.\n\n### Fix\n1. Remove the hardcoded `authToken` from source; generate or require operator configuration at build time or deployment time. 2. Remove `anycableCLIArgs()` from the fingerprint computation, or sanitize it to exclude values of secret-bearing flags before hashing. 3. Add a documented opt-out mechanism for telemetry.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/anycable/anycable"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.6.15"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.6.14"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/anycable/anycable/security/advisories/GHSA-w72w-9qmj-c9qm"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/anycable/anycable/commit/201c67e99e463ed63bd6b345562f4c458385fcee"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/anycable/anycable"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/anycable/anycable/releases/tag/v1.6.15"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-312", "CWE-798" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-18T17:17:29Z",
    "nvd_published_at" : null
  }
}