CVE-2026-65654
8.7Temporal Technologies · ringpop-go
Temporal ringpop-go fails to enforce label limits on SWIM membership changes, allowing unauthenticated remote attackers to trigger resource exhaustion and cause service unavailability.
Executive summary
A high-severity resource exhaustion vulnerability in Temporal ringpop-go allows unauthenticated remote attackers to crash the hosting process via malicious membership updates.
Vulnerability
This is an allocation of resources without limits or throttling (CWE-770) issue where the application fails to validate label maps received via SWIM membership changes. An unauthenticated remote attacker can submit excessive label data, leading to uncontrolled memory and gossip-bandwidth consumption.
Business impact
Successful exploitation results in a denial-of-service condition, rendering the affected service unavailable. Given the CVSS score of 8.7, this represents a significant threat to operational stability and uptime, as the attack vector is network-based and requires no authentication or user interaction.
Remediation
Immediate Action: Upgrade the github.com/temporalio/ringpop-go library to version 0.1.0 or later, which implements the necessary validation of peer-supplied label maps.
Proactive Monitoring: Monitor network traffic for unusual volumes of SWIM membership change requests and track process memory usage for sudden spikes that may indicate exploitation attempts.
Compensating Controls: Implement network-level access controls to restrict access to the Ringpop TChannel listener to trusted peers only, effectively limiting the attack surface.
Exploitation status
Public Exploit Available: Unknown
Analyst recommendation
The potential for service disruption poses a substantial risk to production environments. Administrators should prioritize updating the library immediately, as the lack of authentication requirements makes this vulnerability highly susceptible to remote exploitation.
More Temporal Technologies CVEs
History
- Disclosed CVE record published
- Collected by CVE Brief via github
- Analyst report written
- Published in the daily brief high section
Sources
Originally found and disclosed by An external security researcher who reported this issue responsibly to Temporal Technologies, per the CVE Program record.