Answer in brief
CVE-2025-29923 records a Low severity (CVSS 3.7) vulnerability in go-redis allows potential out of order responses when `CLIENT SETINFO` times out during connection establishment. The current sources do not mark it as known exploited. The current feed maps redis/go-redis (generic), github.com/redis/go-redis/v9 (go), github.com/redis/go-redis/v9 (go), github.com/redis/go-redis/v9 (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 3.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps redis/go-redis (generic), github.com/redis/go-redis/v9 (go), github.com/redis/go-redis/v9 (go), github.com/redis/go-redis/v9 (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| redis/go-redisgeneric | >= 9.7.0-beta.1, < 9.7.2 || >= 9.6.0b1, < 9.6.3 || >= 9.5.1, < 9.5.5 | Not reported |
| github.com/redis/go-redis/v9go | >=9.6.0b1,<9.6.3 | 9.6.3 |
| github.com/redis/go-redis/v9go | >=9.5.1,<9.5.5 | 9.5.5 |
| github.com/redis/go-redis/v9go | >=9.7.0-beta.1,<=9.7.1 | 9.7.3 |
Published upstream
Mar 20, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 2, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 2, 2026
go-redis is the official Redis client library for the Go programming language. Prior to 9.5.5, 9.6.3, and 9.7.2, go-redis potentially responds out of order when `CLIENT SETINFO` times out during connection establishment. This can happen when the client is configured to transmit its identity, there are network connectivity issues, or the client was configured with aggressive timeouts. The problem occurs for multiple use cases. For sticky connections, you receive persistent out-of-order responses for the lifetime of the connection. All commands in the pipeline receive incorrect responses. When used with the default ConnPool once a connection is returned after use with ConnPool#Put the read buffer will be checked and the connection will be marked as bad due to the unread data. This means that at most one out-of-order response before the connection is discarded. This issue is fixed in 9.5.5, 9.6.3, and 9.7.2; however, 9.7.2 has been yanked and 9.7.3 is the lowest available patched version on the 9.7.x branch. As a workaround, set the flag `DisableIndentity` to `true` when constructing the client instance.
Quoted source text, attributed separately from HOL analysis.