AnyCable is a realtime server for reliable two-way communication that supports any backend. Prior to 1.6.15,…
Historical advisory recorded 25 Oct 2026 15:18:45 UTC. Read the latest advisory.
nvd · CVE-2026-63405
PublishedAnyCable 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.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-63405 · CVE overview and exploitation status
nvd · CVE-2026-63405
This historical advisory does not include today's related changes. Open the latest advisory to find current connections.