CVEvulnerability
CVE-2026-63405
5.9 MEDIUM
Official page ↗
- Status
- Deferred
- Published
- 2026-09-18
- Last modified
- 2026-09-24
- Assigner
- [email protected]
- CVSS 3.1 ([email protected])
- 5.9 MEDIUM — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
- Weaknesses
- CWE-345
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.
Related
Weakness · CWE (1)
- CWE-345 Insufficient Verification of Data Authenticity weakness
References
- https://github.com/anycable/anycable/commit/d2cbadec792f038f4695c84a65c0d957b0fde72c github.com
- https://github.com/anycable/anycable/releases/tag/v1.6.15 github.com
- https://github.com/anycable/anycable/security/advisories/GHSA-5p54-whvp-x327 github.com
- https://github.com/anycable/anycable/security/advisories/GHSA-5p54-whvp-x327 github.com