CVE-2026-63405
- Source
- https://cve.org/CVERecord?id=CVE-2026-63405
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-63405.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-63405
- Aliases
- Published
- 2026-09-18T16:47:37Z
- Modified
- 2026-09-20T11:46:33Z
- Severity
-
- 5.9 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N CVSS Calculator
- Summary
- AnyCable: Pusher REST API Does Not Verify Request Body MD5 Enabling Signed-Request Replay with Arbitrary Body
- Details
-
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.
- Database specific
{ "cna_assigner": "GitHub_M", "cwe_ids": [ "CWE-345" ], "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/63xxx/CVE-2026-63405.json" }- References
-
- https://github.com/anycable/anycable/releases/tag/v1.6.15
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/63xxx/CVE-2026-63405.json
- https://github.com/anycable/anycable/security/advisories/GHSA-5p54-whvp-x327
- https://nvd.nist.gov/vuln/detail/CVE-2026-63405
- https://github.com/anycable/anycable/commit/d2cbadec792f038f4695c84a65c0d957b0fde72c