---
id: CVE-2025-29923
title: go-redis is the official Redis client library for the Go programming language
summary: >-
  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 …
severity: low
cvss: 3.7
cvssVector: 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N'
cwe:
  - CWE-20
published: '2025-03-20'
updated: '2026-09-03'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2025-29923'
references:
  - url: >-
      https://github.com/redis/go-redis/commit/d236865b0cfa1b752ea4b7da666b1fdcd0acebb6
    label: security-advisories@github.com
  - url: 'https://github.com/redis/go-redis/pull/3295'
    label: security-advisories@github.com
  - url: 'https://github.com/redis/go-redis/security/advisories/GHSA-92cp-5422-2mw7'
    label: security-advisories@github.com
tags:
  - nvd
epss: 0.00737
epssPercentile: 0.52469
ingestedAt: '2026-09-03T03:55:21.925Z'
---

## Overview

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 retracted 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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.