BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-29923High confidence

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

redis · go-redis

Official source article: GitHub GHSA-92CP-5422-2MW7 ↗. Check the applicable product and release in the original source.

3.7LowCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Low technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 58 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityLowOperational priority:Low, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.74% for the current model date.

Compensating controls

  • Apply the linked authoritative mitigation while planning the permanent fix.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs redis go-redis and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 58 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

3 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian forkyforky · sourcegolang-github-go-redis-redisNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcegolang-github-go-redis-redisNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivegolang-github-go-redis-redisUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges6 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Gogithub.com/redis/go-redis/v9SEMVER: introduced 9.7.0-beta.1; fixed 9.7.39.7.3OSV record ↗aggregator derived · 10 Sep 2026
Gogithub.com/redis/go-redis/v9ECOSYSTEM: introduced 9.6.0b1; fixed 9.6.39.6.3OSV record ↗aggregator derived · 10 Sep 2026
Gogithub.com/redis/go-redis/v9SEMVER: introduced 9.5.1; fixed 9.5.59.5.5OSV record ↗aggregator derived · 10 Sep 2026
gogithub.com/redis/go-redis/v9>= 9.6.0b1, < 9.6.39.6.3GitHub advisory ↗upstream repository advisory · 2 Sep 2026
gogithub.com/redis/go-redis/v9>= 9.5.1, < 9.5.59.5.5GitHub advisory ↗upstream repository advisory · 2 Sep 2026
gogithub.com/redis/go-redis/v9>= 9.7.0-beta.1, <= 9.7.19.7.3GitHub advisory ↗upstream repository advisory · 2 Sep 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2025-29923 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitygithub.com/redis/go-redis: go-redis allows potential out of order responses when `CLIENT SETINFO` times out during connection establishment
58 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • cryostat/cryostat-storage-rhel9 as a component of Cryostat 4
  • custom-metrics-autoscaler/custom-metrics-autoscaler-adapter-rhel8 as a component of Custom Metric Autoscaler operator for Red Hat Openshift
  • custom-metrics-autoscaler/custom-metrics-autoscaler-adapter-rhel9 as a component of Custom Metric Autoscaler operator for Red Hat Openshift
  • custom-metrics-autoscaler/custom-metrics-autoscaler-admission-webhooks-rhel8 as a component of Custom Metric Autoscaler operator for Red Hat Openshift
  • custom-metrics-autoscaler/custom-metrics-autoscaler-admission-webhooks-rhel9 as a component of Custom Metric Autoscaler operator for Red Hat Openshift
  • custom-metrics-autoscaler/custom-metrics-autoscaler-rhel8 as a component of Custom Metric Autoscaler operator for Red Hat Openshift
  • custom-metrics-autoscaler/custom-metrics-autoscaler-rhel9 as a component of Custom Metric Autoscaler operator for Red Hat Openshift
  • custom-metrics-autoscaler/custom-metrics-autoscaler-rhel9-operator as a component of Custom Metric Autoscaler operator for Red Hat Openshift
  • openshift-logging/logging-loki-rhel9 as a component of Logging Subsystem for Red Hat OpenShift
  • multiarch-tuning/multiarch-tuning-operator-bundle as a component of Multiarch Tuning Operator
  • multiarch-tuning/multiarch-tuning-rhel9-operator as a component of Multiarch Tuning Operator
  • multicluster-globalhub/multicluster-globalhub-grafana-rhel9 as a component of Multicluster Global Hub
Summary
A flaw was found in go-redis. This vulnerability allows out-of-order responses and incorrect command execution via CLIENT SETINFO timeouts during connection establishment, potentially leading to data inconsistency.
Remediation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-7158

No EUVD known-exploited evidence

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.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
3.7 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Low technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 58 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Improper Input Validation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-20 ↗

CWE-20: Improper Input Validation. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.ILowIntegrity impact: A successful attack can cause a limited loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-20
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2025-7158Official EUVD mapping

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.

Official EUVD record ↗
BSI · German · WID-SEC-2025-0633Gitea: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Gitea ausnutzen, um Daten zu manipulieren, oder einen Denial of Service auszulösen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250326Security Bulletin 26 Mar 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 26 Mar 2025, published on 26 March 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0315Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-15224 Référence CVE CVE-2025-15282 https://www.cve.org/CVERecord?id=CVE-2025-15282 Référence CVE CVE-2025-15366 https://www.cve.org/CVERecord?id=CVE-2025-15366 Référence CVE CVE-2025-15367 https://www.cve.org/CVERecord?id=CVE-2025-15367 Référence CVE CVE-2025-22870 https://www.cve.org/CVERecord?id=CVE-2025-22870 Référence CVE CVE-2025-22872 https://www.cve.org/CVERecord?id=CVE-2025-22872 Référence CVE CVE-2025-24358 https://www.cve.org/CVERecord?id=CVE-2025-24358 Référence CVE CVE-2025-27219 https://www.cve.org/CVERecord?id=CVE-2025-27219 Référence CVE CVE-2025-27220 https://www.cve.org/CVERecord?id=CVE-2025-27220 Référence CVE CVE-2025-29923 https://www.cve.org/CVERecord?id=CVE-2025-29923 Référence CVE CVE-2025-30749 https://www.cve.org/CVERecord?id=CVE-2025-30749 Référence CVE CVE-2025-30754 https://www.cve.org/CVERecord?id=CVE-2025-30754 Référence CVE CVE-2025-31115 https://www.cve.org/CVERecord?id=CVE-2025-31115 Référence CVE CVE-2025-47273 https://www.cve.org/CVERecord?id=CVE-2025-47273 Référence CVE CVE-2025-47909 https://www.cve.org/CVERecord?id=CVE-2025-47909 Référence CVE CVE-2025-47910 https://www.cve.org/CVERecord?id=CVE-2025-47910 Référence CVE CVE-2025-47912 https://www.cve.org/CVERecord?id=CVE-2025-47912 Référence CVE CVE-2025-47914 https://www.cve.org/CVERecord?id=

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
04

Evidence and provenance

Published 20 Mar 2025 · Last source change 2 Sept 2026, 21:19 UTC · CWE-20 · Improper Input Validation

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-7158
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD not scheduled

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    go-redis: >= 9.7.0-beta.1, < 9.7.3, >= 9.6.0b1, < 9.6.3, >= 9.5.1, < 9.5.5 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    go-redis: >= 9.7.0-beta.1, < 9.7.2, >= 9.6.0b1, < 9.6.3, >= 9.5.1, < 9.5.5 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    >= 9.7.0-beta.1, < 9.7.3; >= 9.6.0b1, < 9.6.3; >= 9.5.1, < 9.5.5 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    >= 9.7.0-beta.1, < 9.7.2; >= 9.6.0b1, < 9.6.3; >= 9.5.1, < 9.5.5 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    >= 9.7.0-beta.1, < 9.7.2; >= 9.6.0b1, < 9.6.3; >= 9.5.1, < 9.5.5 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    go-redis: >= 9.7.0-beta.1, < 9.7.3, >= 9.6.0b1, < 9.6.3, >= 9.5.1, < 9.5.5 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
ENISA EUVD · EUVD-2025-7158↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference · GitHub GHSA-92CP-5422-2MW7↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-29923 · cve.blacktree.nl