Service interruption via unbounded Redis request buffering
Published Sep 21, 2026 · Updated Sep 21, 2026
Resource exhaustion in Thinkst Applied Research OpenCanary before 0.9.10 allows remote attackers to interrupt service through its Redis module. RedisProtocol.dataReceived retains incomplete unauthenticated requests in a per-connection buffer without size, connection-count, or idle-time limits. The Redis module must be enabled and network-reachable; sustained partial requests exhaust process memory and interrupt the honeypot.
Summary
What happened
Resource exhaustion in Thinkst Applied Research OpenCanary before 0.9.10 allows remote attackers to interrupt service through its Redis module. RedisProtocol.dataReceived retains incomplete unauthenticated requests in a per-connection buffer without size, connection-count, or idle-time limits. The Redis module must be enabled and network-reachable; sustained partial requests exhaust process memory and interrupt the honeypot.
The record
- CVE
- CVE-2026-85219
- Published
- Sep 21, 2026
- Updated
- Sep 21, 2026
- Vendor
- Thinkst Applied Research
- Product
- OpenCanary
- Classifications
- CWE-770, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 21, 2026CVE publishedPublication date reported by the CVE source.
- Sep 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.4 <0.9.10
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started