CVE-2026-63405
Description
A flaw was found in AnyCable. The Pusher-compatible REST API does not verify the integrity of request bodies, allowing a remote attacker to manipulate signed requests. An attacker can capture a legitimate signed POST request and replace its body with arbitrary content. The absence of a timestamp freshness check further allows these forged requests to be replayed indefinitely. This can lead to forged server-side events, modification of application state, or delivery of attacker-controlled messages to WebSocket clients.
Statement
This vulnerability is rated as Moderate impact because an attacker cannot forge signatures directly and must first intercept a legitimately signed HTTP request to exploit the flaw. Successful exploitation allows unauthorized broadcasting of arbitrary event payloads over Pusher-compatible endpoints without knowing the shared signing secret. However, AnyCable is not shipped or supported in Red Hat Enterprise Linux or core platform products, significantly limiting overall exposure across standard Red Hat environments.
Understanding the Weakness (CWE)
Integrity,Other
Technical Impact: Modify Application Data; Other
Integrity checks usually use a secret key that helps authenticate the data origin. Skipping integrity checking generally opens up the possibility that new data from an invalid source can be injected.
Integrity,Other
Technical Impact: Other
Data that is parsed and used may be corrupted.
Non-Repudiation,Other
Technical Impact: Hide Activities; Other
Without a checksum check, it is impossible to determine if any changes have been made to the data after it was sent.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
