go-redis allows potential out of order responses when `CLIENT SETINFO` times out during connection establishment
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
cve-program · CVE-2025-29923
Publishedgo-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.
- Source published
- 20 Mar 2025 18:03:14 UTC
- Source modified
- 2 Sep 2026 21:19:29 UTC
- Saved here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
euvd · EUVD-2025-7158
Publishedgo-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.
Additional publisher context
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
- Source published
- Mar 20, 2025, 6:03:14 PM (timezone not stated)
- Source modified
- Sep 2, 2026, 9:19:29 PM (timezone not stated)
- Saved here
- 15 Nov 2026 03:40:19 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
EUVD CVSS 3.1 · 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
nvd · CVE-2025-29923
Publishedgo-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.
Additional publisher context
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
- Source published
- 20 Mar 2025 18:15:19 UTC
- Source modified
- 3 Sep 2026 13:04:17 UTC
- Saved here
- 25 Oct 2026 02:24:42 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · [email protected] · Secondary · 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
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
- Source published
- 20 Mar 2025 18:49:59 UTC
- Source modified
- 10 Sep 2026 03:50:23 UTC
- Saved here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V3 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
Publisher rating · LOW
osv · GO-2025-3540
PublishedPotential out of order responses when CLIENT SETINFO times out during connection establishment in github.com/redis/go-redis
- Source published
- 26 Mar 2025 17:24:24 UTC
- Source modified
- 4 Feb 2026 03:06:24 UTC
- Saved here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.