CVE-2026-63406

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 84% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

AnyCable is a realtime server for reliable two-way communication that supports any backend. Prior to 1.6.15, the telemetry subsystem in telemetry/config.go enables tracking with a hardcoded public authToken, while clusterFingerprint in telemetry/telemetry.go reads the full configuration file and raw os.Args returned by anycableCLIArgs, including values supplied through --secret, --jwt_secret, and --http_rpc_secret. These inputs are passed to generateDigest, where sha256.New produces the hexadecimal fingerprint that is sent as telemetry. The available source therefore does not show raw credentials leaving the process or establish the advisory's claimed confidentiality loss, although the stable fingerprint is derived from secret-bearing configuration and the default telemetry client uses publicly known authentication material. This issue is fixed in version 1.6.15.

CVSS v3
5.9
EG Score
5.9(medium)
EG Risk
43(Track)
EG Risk 43/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity59% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

September 18, 2026

Last Modified

September 18, 2026

Advisory Details (3)

Auto-updated Sep 18, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github_release Patch Available

1.6.15

Patch available: anycable/anycable v1.6.15

https://github.com/anycable/anycable/releases/tag/v1.6.15
github_commit

commit 201c67e99e46 (anycable/anycable)

Fix landed in anycable/anycable commit 201c67e99e46 — awaiting tagged release

https://github.com/anycable/anycable/commit/201c67e99e463ed63bd6b345562f4c458385fcee
github Patch Available🟡 PoC Available

Telemetry Subsystem Contains Hardcoded Authentication Token and Transmits CLI Arguments Including Secrets · Advisory · anycable/anycable · GitHub

https://github.com/anycable/anycable/security/advisories/GHSA-w72w-9qmj-c9qm

Vendor Advisories for CVE-2026-63406(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 5× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 19:56 UTCEG score recompute
  2. 2026-09-18 18:27 UTCEG score recompute
  3. 2026-09-18 17:19 UTCEG score recompute
  4. 2026-09-18 16:59 UTCEG score recompute
  5. 2026-09-18 16:59 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-63406?
CVE-2026-63406 is a medium vulnerability published on September 18, 2026. AnyCable is a realtime server for reliable two-way communication that supports any backend. Prior to 1.6.15, the telemetry subsystem in telemetry/config.go enables tracking with a hardcoded public authToken, while clusterFingerprint in telemetry/telemetry.go reads the full configuration file and…
When was CVE-2026-63406 disclosed?
CVE-2026-63406 was first published in the National Vulnerability Database on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63406 actively exploited?
CVE-2026-63406 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 83.9% of all scored CVEs.
What is the CVSS score of CVE-2026-63406?
CVE-2026-63406 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-63406?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63406, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-63406

Explore →

Is Your Infrastructure Affected by CVE-2026-63406?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs