CVE-2026-63405CWE-345

CVE-2026-63405

Medium · published September 18, 2026

CVSS v3.1
5.9
EPSS
0%
Percentile
10.4
In the wild
Unconfirmed
What it is

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.

The record
Technical detail
CVSS v3.1
5.9 · MEDIUM
Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
CVSS v4.0
Not supplied
EPSS
0.00209 · 10.4th percentile
Weakness
CWE-345 · Insufficient Verification of Data Authenticity
Published
2026-09-18T21:16Z
References (4)
EPSS history
Timeline
  • 20 SEP 03:23Z
    EPSS moved — → 0%
    epss
  • 18 SEP 16:47Z
    AnyCable: Pusher REST API Does Not Verify Request Body MD5 Enabling Signed-Request Replay with Arbitrary Body
    cvelistv5