Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
AnyCable versions before 1.6.15 do not check that the body of a signed Pusher-compatible REST API request matches the body MD5 included in the signature. An attacker who can observe one signed request, for example from logs or a network tap, can replay it with a different body and broadcast arbitrary events to any channel, with no timestamp expiry. Upgrade to AnyCable 1.6.15 or later, which is the listed fixed version.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.9 | Medium | 3.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0021, the 11th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:12 UTC First seen by agentprime
- 31 Oct 2026, 14:12 UTC Confirmed by OSV