CVE-2026-63405

Medium

Description

AnyCable is a realtime server for reliable two-way communication that supports any backend. Prior to 1.6.15, the Pusher-compatible REST API in pusher/http.go includes the caller-supplied body_md5 value in the HMAC input but does not calculate the digest of the received request body or compare it with the signed value. An attacker who obtains a legitimate signed POST request can retain its query parameters and auth_signature while replacing the body, causing Handler and handleEvents to accept and broadcast attacker-selected event content. The absence of an auth_timestamp freshness check also allows the captured signature to be replayed indefinitely. This can forge server-side events, modify application state, or deliver attacker-controlled messages to WebSocket clients within the signed request's application context. This issue is fixed in version 1.6.15.

SeverityMedium
CVSS5.9
Exploit probability—
ProductGithub.com/anycable/anycable
PublishedSep 18, 2026
First seenSep 18, 2026
Weakness typeCWE-345CWE-345

How to fix

Update
  • github.com/anycable/anycable1.6.15 or later

Affected products

ProductAffected versionsFixed in
github.com/anycable/anycableGov < 1.6.151.6.15
github.com/anycable/anycable-goGoNo range specified—

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.