Skip to content

CVE-2026-63405 AnyCable: Pusher REST API Does Not Verify Request Body MD5 Enabling Signed-Request Replay with Arbitrary Body

MediumCVSS 5.9 EPSS 0.21%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
Proof of concept public · automatable: no · technical impact: partial

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.

Upgrade path

3 packages: 1 fixed, 1 with no fix yet.

PackageAffectedFixed inStatus
anycable github.com/anycable/anycable-go(Go) All versions No fix listed No fix yet
anycable(Go) < 1.6.15; <= 1.6.14 1.6.15 Fixed
anycable = < 1.6.15 No fix listed Versions listed

Affected products

ProductAffected versionsFixed in
anycable = < 1.6.15 No fix listed
anycable(Go) < 1.6.15 1.6.15
anycable github.com/anycable/anycable-go(Go) All versions No fix listed
anycable(Go) <= 1.6.14 No fix listed

References