CVE-2026-63405: AnyCable Pusher REST API Does Not Vulnerability

MODERATE
Advisory Identifier: GHSA-5p54-whvp-x327
CVSS 5.9
CWE-345
Published
Advisory Summary

CVE-2026-63405 is a MODERATE (CVSS 5.9) pusher rest api does not vulnerability (CWE-345: Insufficient Verification of Data Authenticity) affecting AnyCable libraries in the Go ecosystem. The issue involves pusher rest api does not verify request body md5 enabling signed-request replay with arbitrary body. Remediation is available by upgrading affected packages to version 1.6.15.

CVE-2026-63405 at a Glance

CVE Identifier CVE-2026-63405
GHSA Identifier GHSA-5p54-whvp-x327
Severity MODERATE
CVSS v3.1 Base Score 5.9
CWE Classification CWE-345: Insufficient Verification of Data Authenticity
Affected Product AnyCable
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 5.9

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-63405

To remediate this vulnerability, upgrade all affected AnyCable dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/anycable/anycable fixed: 1.6.15
Upgrade github.com/anycable/anycable to 1.6.15
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/anycable/anycable

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-63405, inspect your project dependencies for AnyCable:

inspect dependencies for github.com/anycable/anycable

Analyze the terminal output to locate any version of AnyCable in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.6.15), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-345: Insufficient Verification of Data Authenticity, where the product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. In AnyCable, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary The Pusher-compatible REST API includes `body_md5` in the HMAC signature string but never computes or verifies the MD5 of the received HTTP body, allowing anyone who observes a signed request to replay it with an entirely different body. ### Details In `pusher/http.go`, the `Handler` function extracts `body_md5` from the URL query string (line 169) and includes it verbatim in `stringToSign` (line 175). It then verifies `HMAC(stringToSign, secret) == auth_signature`. After verification succeeds, `handleEvents` reads and parses `r.Body` (lines 201-212) without ever computing `md5(body)` and comparing it against the `body_md5` that was signed. The Pusher protocol specification explicitly requires the server to verify this digest to prevent body-substitution attacks. There is also no `auth_timestamp` staleness check, so replays are valid indefinitely. ### PoC 1. Capture a legitimate signed POST to `/apps/<app_id>/events?auth_key=K&auth_timestamp=T&auth_version=1.0&body_md5=LEGIT_MD5&auth_signature=SIG` carrying body `{"name":"safe-event","channel":"ch","data":"..."}` (e.g., from TLS-terminating load-balancer logs). 2. Send a new request with the same query string parameters but a different body: `{"name":"injected-event","channel":"admin","data":"malicious-payload"}` 3. The server accepts the request (HMAC over `stringToSign` matches the original) and broadcasts the injected event to all subscribers of `admin`. ### Impact An attacker who can read any single signed Pusher API request (from logs, a shared proxy, or a network tap) can broadcast arbitrary events to any channel indefinitely, potentially forging server-side events, corrupting application state, or delivering phishing messages to WebSocket clients. ### Fix After reading `r.Body`, compute `hex(md5(body))` and compare it to the `body_md5` query parameter using a constant-time comparison before proceeding. Additionally, reject requests whose `auth_timestamp` is more than 600 seconds from the current time.

CVE-2026-63405 Affected AnyCable Versions

1 component(s)
Fixed Versions:
1.6.15
Product / Package Ecosystem Affected Versions Fixed Version
github.com/anycable/anycable
Go
< 1.6.15
1.6.15

References

Frequently Asked Questions

What is CVE-2026-63405?
CVE-2026-63405 is a security vulnerability in AnyCable involving Pusher REST API Does Not Verify Request Body MD5 Enabling Signed-Request Replay with Arbitrary Body under CWE-345: Insufficient Verification of Data Authenticity.
Which AnyCable versions are affected?
Affected versions include releases prior to 1.6.15 across affected packages: github.com/anycable/anycable.
What version fixes CVE-2026-63405?
Upgrading to 1.6.15 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/anycable/anycable affected?
Yes, github.com/anycable/anycable is affected in releases prior to 1.6.15. Upgrade your dependency to 1.6.15 or later.
What is the CVSS score of CVE-2026-63405?
CVE-2026-63405 has a CVSS v3.1 base score of 5.9 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N.
What CWE is associated with CVE-2026-63405?
CVE-2026-63405 is classified under CWE-345: Insufficient Verification of Data Authenticity (The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.).
How can I check Go dependencies for CVE-2026-63405?
Run the dependency tree command: 'inspect dependencies for github.com/anycable/anycable'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-5p54-whvp-x327",
  "modified" : "2026-09-18T17:16:25Z",
  "published" : "2026-09-18T17:16:25Z",
  "aliases" : [ "CVE-2026-63405" ],
  "summary" : "AnyCable: Pusher REST API Does Not Verify Request Body MD5 Enabling Signed-Request Replay with Arbitrary Body",
  "details" : "### Summary\nThe Pusher-compatible REST API includes `body_md5` in the HMAC signature string but never computes or verifies the MD5 of the received HTTP body, allowing anyone who observes a signed request to replay it with an entirely different body.\n\n### Details\nIn `pusher/http.go`, the `Handler` function extracts `body_md5` from the URL query string (line 169) and includes it verbatim in `stringToSign` (line 175). It then verifies `HMAC(stringToSign, secret) == auth_signature`. After verification succeeds, `handleEvents` reads and parses `r.Body` (lines 201-212) without ever computing `md5(body)` and comparing it against the `body_md5` that was signed. The Pusher protocol specification explicitly requires the server to verify this digest to prevent body-substitution attacks. There is also no `auth_timestamp` staleness check, so replays are valid indefinitely.\n\n### PoC\n1. Capture a legitimate signed POST to `/apps/<app_id>/events?auth_key=K&auth_timestamp=T&auth_version=1.0&body_md5=LEGIT_MD5&auth_signature=SIG` carrying body `{\"name\":\"safe-event\",\"channel\":\"ch\",\"data\":\"...\"}` (e.g., from TLS-terminating load-balancer logs).\n2. Send a new request with the same query string parameters but a different body:\n   `{\"name\":\"injected-event\",\"channel\":\"admin\",\"data\":\"malicious-payload\"}`\n3. The server accepts the request (HMAC over `stringToSign` matches the original) and broadcasts the injected event to all subscribers of `admin`.\n\n### Impact\nAn attacker who can read any single signed Pusher API request (from logs, a shared proxy, or a network tap) can broadcast arbitrary events to any channel indefinitely, potentially forging server-side events, corrupting application state, or delivering phishing messages to WebSocket clients.\n\n### Fix\nAfter reading `r.Body`, compute `hex(md5(body))` and compare it to the `body_md5` query parameter using a constant-time comparison before proceeding. Additionally, reject requests whose `auth_timestamp` is more than 600 seconds from the current time.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/anycable/anycable"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.6.15"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.6.14"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/anycable/anycable/security/advisories/GHSA-5p54-whvp-x327"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/anycable/anycable/commit/d2cbadec792f038f4695c84a65c0d957b0fde72c"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/anycable/anycable"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/anycable/anycable/releases/tag/v1.6.15"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-345" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-18T17:16:25Z",
    "nvd_published_at" : null
  }
}