Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

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

Quick assessment

Affected
anycable anycable
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

AnyCable 是一个支持任意后端的实时服务器，用于实现可靠的双向通信。在 1.6.15 版本之前，位于 中的 Pusher 兼容 REST API 在计算 HMAC 输入时包含了调用方提供的 值，但并未对接收到的请求体计算摘要，也未将其与签名值进行比较。攻击者若获取到一个合法的带签名的 POST 请求，可以保留其查询参数和 ，同时替换请求体内容，从而使得 和 接受并广播由攻击者选择的事件内容。此外，由于缺少对 的新鲜度检查，捕获的签名可以被无限期重放。这可能导致伪造服务端事件、修改应用程序状态，或将攻击者控制的

CVSS 5.9 · Medium

Affected Version Matrix 1

VendorProduct Version RangeStatus
anycable anycable < 1.6.15 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-63405

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
AnyCable: Pusher REST API Does Not Verify Request Body MD5 Enabling Signed-Request Replay with Arbitrary Body
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
对数据真实性的验证不充分
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
anycable anycable < 1.6.15 -

II. Public POCs for CVE-2026-63405

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-63405

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-63405 (1)

Other References for CVE-2026-63405 (2)

IV. Related Vulnerabilities

Same product: anycable
Same vendor: anycable
Same weakness: CWE-345

V. Comments for CVE-2026-63405

No comments yet

Leave a comment