Thinkst Patches Canary Redis Denial of Service
Tech GuruQuick Answer
The authority published CVE-2026-85220 for Thinkst Canary platforms with Redis enabled, beginning at the platform-specific first vulnerable releases. A vulnerability in the Thinkst Canary honeypot Redis service allows an unauthenticated remote attacker to execute a Denial-of-Service attack against the honeypot. The vulnerability is accessible when the Redis service is enabled only. The Canary is NOT affected if the Redis service is disabled. Thinkst has addressed this issue on all supported platforms. New update files to address this issue are available on all platforms except Docker. For Docker customers, a new Docker image has been published which includes the patch. Customers with automatic updates enabled already have updates in distribution. If automatic updates are disabled, customers are advised to update their Canaries. Workarounds are available for customers unable to update at this time. Affected deployments should be matched to the authority's exact scope and moved to the supported fixed release.
Confirm Scope And Apply The Supported Fix
What to do now: Inventory Thinkst Canary platforms with Redis enabled, beginning at the platform-specific first vulnerable releases, match the exact affected release or feature, apply the authority-supported fixed build or service remediation, validate the dependent workflow, and preserve evidence.
Last verified: 2026-09-21 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | Thinkst Canary platforms with Redis enabled, beginning at the platform-specific first vulnerable releases |
|---|---|
| Advisory | TC-2026-01 |
| CVE | CVE-2026-85220 |
| Authoritative release date | 2026-09-21 13:13:53.053 UTC |
| Authority revision date | 2026-09-21 14:48:17.169 UTC |
| Affected versions | Thinkst Canary platforms with Redis enabled, beginning at the platform-specific first vulnerable releases |
| Fixed version | AWS/GCP/Tailscale 5.3.2; Docker 5.7.2; Hardware 5.1.2; Azure 5.6.4; Hyper-V 5.5.2; Nutanix 5.9.2; OCI 5.11.2; OpenStack 5.8.2; VMware 5.2.2 |
| CVSS base score | 3.7 (CVSS v3.1) |
| CVSS severity | Low |
| Exploitation status | Thinkst is not aware of public announcements or malicious use; no exploitation claim is inferred. |
What Changed
A vulnerability in the Thinkst Canary honeypot Redis service allows an unauthenticated remote attacker to execute a Denial-of-Service attack against the honeypot. The vulnerability is accessible when the Redis service is enabled only. The Canary is NOT affected if the Redis service is disabled. Thinkst has addressed this issue on all supported platforms. New update files to address this issue are available on all platforms except Docker. For Docker customers, a new Docker image has been published which includes the patch. Customers with automatic updates enabled already have updates in distribution. If automatic updates are disabled, customers are advised to update their Canaries. Workarounds are available for customers unable to update at this time.
What To Validate Now
- Inventory. Locate Thinkst Canary platforms with Redis enabled, beginning at the platform-specific first vulnerable releases deployments, versions, enabled features, exposure paths, owners, and dependent services.
- Establish applicability. Compare each deployment with the authority's affected-version statement: Thinkst Canary platforms with Redis enabled, beginning at the platform-specific first vulnerable releases Do not infer applicability from product family or severity alone.
- Remediate. Apply AWS/GCP/Tailscale 5.3.2; Docker 5.7.2; Hardware 5.1.2; Azure 5.6.4; Hyper-V 5.5.2; Nutanix 5.9.2; OCI 5.11.2; OpenStack 5.8.2; VMware 5.2.2 through the supported vendor or project channel, following the current advisory and change-control requirements.
- Validate. Confirm the resulting version or managed-service state, exercise representative functionality and recovery paths, monitor for regressions, and document exceptions.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
