Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

go-redis · Vulnerability

cve-program · CVE-2025-29923

Published

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.

Read the publisher's advisory

euvd · EUVD-2025-7158

Published

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.

Read the publisher's advisory

nvd · CVE-2025-29923

Published

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.

Read the publisher's advisory

osv · GHSA-92cp-5422-2mw7

Published

### Impact The issue only occurs when the `CLIENT SETINFO` command times out during connection establishment. The following circumstances can cause such a timeout: 1. The client is configured to transmit its identity. This can be disabled via the `DisableIndentity` flag. 2. There are network connectivity issues 3. The client was configured with aggressive timeouts The impact differs by use case: * **Sticky connections**: Rather than using a connection from the pool on-demand, the caller can stick with a connection. Then you receive persistent out-of-order responses for the lifetime of the connection. * **Pipelines**: All commands in the pipeline receive incorrect responses. * **Default connection pool usage without pipelining**: When used with the default [ConnPool](https://github.com/redis/go-redis/blob/8fadbef84a3f4e7573f8b38e5023fd469470a8a4/internal/pool/pool.go#L77) once a connection is returned after use with [ConnPool#Put](https://github.com/redis/go-redis/blob/8fadbef84a3f4e7573f8b38e5023fd469470a8a4/internal/pool/pool.go#L366) 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. ### Patches We prepared a fix in https://github.com/redis/go-redis/pull/3295 and plan to release patch versions soon. Versions 9.7.2, 9.6.3, and 9.5.5 were patched. However, 9.7.2 has been yanked, making 9.7.3 the lowest available 9.7.x version with a patch. ### Workarounds You can prevent the vulnerability by setting the flag `DisableIndentity` (BTW: We also need to fix the spelling.) to `true` when constructing the client instance. ### Credit Akhass Wasti Ramin Ghorashi Anton Amlinger Syed Rahman Mahesh Venkateswaran Sergey Zavoloka Aditya Adarwal Abdulla Anam Abd-Alhameed Alex Vanlint Gaurav Choudhary Vedanta Jha Yll Kelani Ryan Picard

Read the publisher's advisory

osv · GO-2025-3540

Published

Potential out of order responses when CLIENT SETINFO times out during connection establishment in github.com/redis/go-redis

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2025-29923

Published

go-redis

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "redis",
                    "product": "go-redis",
                    "versions": [
                        {
                            "version": ">= 9.7.0-beta.1, < 9.7.2",
                            "status": "affected"
                        },
                        {
                            "version": ">= 9.6.0b1, < 9.6.3",
                            "status": "affected"
                        },
                        {
                            "version": ">= 9.5.1, < 9.5.5",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2025-7158

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Mar 20, 2025, 6:03:14 PM

dateUpdated: Sep 2, 2026, 9:19:29 PM

12 related source bulletins · separate from aliases

openSUSE-SU-2025:15508-1: rekor-1.4.1-1.1 on GA media

CVE-2025-29923 · CVE-2025-58058

SUSE-SU-2025:01989-1: Security update for Multi-Linux Manager Client Tools

CVE-2023-45288 · CVE-2024-9264 · CVE-2024-9476 · CVE-2025-22870 · CVE-2025-22872 · CVE-2025-2703 · CVE-2025-29923 · CVE-2025-3454

WID-SEC-W-2025-0633: Gitea: Mehrere Schwachstellen

CVE-2025-29923 · CVE-2025-30204

SUSE-SU-2025:01991-1: Security update for grafana

CVE-2023-45288 · CVE-2024-9264 · CVE-2024-9476 · CVE-2025-22870 · CVE-2025-22872 · CVE-2025-2703 · CVE-2025-29923 · CVE-2025-3454

SUSE-SU-2026:0383-1: Security update for rekor

CVE-2025-29923 · CVE-2025-58058

SUSE-SU-2026:2258-1: Security update for grafana

CVE-2025-29923 · CVE-2026-21724 · CVE-2026-21725 · CVE-2026-26958 · CVE-2026-27876 · CVE-2026-27877 · CVE-2026-27879 · CVE-2026-28375 · CVE-2026-33186 · CVE-2026-33375 · CVE-2026-34986 · CVE-2026-41602

SUSE-SU-2026:2243-1: Security update 5.0.8 for Multi-Linux Manager Client Tools

CVE-2022-21698 · CVE-2025-29923 · CVE-2026-21724 · CVE-2026-21725 · CVE-2026-26958 · CVE-2026-27606 · CVE-2026-27876 · CVE-2026-27877 · CVE-2026-27879 · CVE-2026-28375 · CVE-2026-33186 · CVE-2026-33375 · CVE-2026-34986 · CVE-2026-40179 · CVE-2026-41602 · CVE-2026-42151 · CVE-2026-42154

openSUSE-SU-2025:15052-1: grafana-11.5.4-1.1 on GA media

CVE-2024-6104 · CVE-2025-2703 · CVE-2025-29923 · CVE-2025-30204 · CVE-2025-3454

SUSE-SU-2025:01987-1: Security update for Multi-Linux Manager Client Tools

CVE-2023-45288 · CVE-2024-9264 · CVE-2024-9476 · CVE-2025-22870 · CVE-2025-22872 · CVE-2025-2703 · CVE-2025-29923 · CVE-2025-3454

openSUSE-SU-2026:20654-1: Security update for grafana

CVE-2023-45288 · CVE-2024-11741 · CVE-2024-28180 · CVE-2024-45339 · CVE-2024-51744 · CVE-2024-9264 · CVE-2024-9476 · CVE-2025-11065 · CVE-2025-21613 · CVE-2025-22870 · CVE-2025-22872 · CVE-2025-2703 · CVE-2025-27144 · CVE-2025-29923 · CVE-2025-3415 · CVE-2025-3454 · CVE-2025-3580 · CVE-2025-4123 · CVE-2025-47911 · CVE-2025-58190 · CVE-2025-6023 · CVE-2025-6197 · CVE-2025-64751 · CVE-2025-68156 · CVE-2026-21720 · CVE-2026-21721 · CVE-2026-21722

openSUSE-SU-2025:14937-1: govulncheck-vulndb-0.0.20250327T184518-1.1 on GA media

CVE-2024-25132 · CVE-2024-53348 · CVE-2024-53351 · CVE-2024-7598 · CVE-2024-7631 · CVE-2024-9042 · CVE-2024-9900 · CVE-2025-1097 · CVE-2025-1098 · CVE-2025-1472 · CVE-2025-1767 · CVE-2025-1974 · CVE-2025-24513 · CVE-2025-24514 · CVE-2025-24920 · CVE-2025-25068 · CVE-2025-25274 · CVE-2025-27612 · CVE-2025-27715 · CVE-2025-27933 · CVE-2025-29778 · CVE-2025-29914 · CVE-2025-29922 · CVE-2025-29923 · CVE-2025-30077 · CVE-2025-30153 · CVE-2025-30162 · CVE-2025-30163 · CVE-2025-30179 · CVE-2025-30204

msrc_CVE-2025-29923: go-redis allows potential out of order responses when `CLIENT SETINFO` times out during connection establishment

CVE-2025-29923

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2025-29923

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Deferred

Weakness classifications: CWE-20

Original publisher date fields

published: 2025-03-20T18:15:19.230

lastModified: 2026-09-03T13:04:17.697

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-92cp-5422-2mw7

Published

github.com/redis/go-redis/v9

Go

SEMVER · introduced 9.7.0-beta.1 → fixed 9.7.3

github.com/redis/go-redis/v9

Go

ECOSYSTEM · introduced 9.6.0b1 → fixed 9.6.3

github.com/redis/go-redis/v9

Go

SEMVER · introduced 9.5.1 → fixed 9.5.5

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2025-3540

Published

github.com/redis/go-redis

Go

SEMVER · introduced 0

github.com/redis/go-redis

Go

SEMVER · introduced 0

github.com/redis/go-redis

Go

SEMVER · introduced 0

github.com/redis/go-redis/v7

Go

SEMVER · introduced 0

github.com/redis/go-redis/v8

Go

SEMVER · introduced 0

github.com/redis/go-redis/v9

Go

SEMVER · introduced 9.5.1 → fixed 9.5.5

github.com/redis/go-redis/v9

Go

SEMVER · introduced 0 → fixed 9.6.3

github.com/redis/go-redis/v9

Go

SEMVER · introduced 9.7.0-beta.1 → fixed 9.7.3

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 12:50 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current