CVE-2026-63405
AnyCable is a realtime server for reliable two-way communication …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/anycable/anycable/commit/d2cbadec792f038f4695c84a65c0d957b0fde72c
- github.com/anycable/anycable/releases/tag/v1.6.15
- github.com/anycable/anycable/security/advisories/GHSA-5p54-whvp-x327
- github.com/advisories/GHSA-5p54-whvp-x327
- nvd.nist.gov/vuln/detail/CVE-2026-63405
- cve.org/CVERecord?id=CVE-2026-63405
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.