What is CVE-2025-29923?

CVE-2025-29923 is a low-severity improper input validation vulnerability in github.com/redis/go-redis/v9 (go), affecting versions >= 9.7.0-beta.1, < 9.7.3. It is fixed in 9.7.3, 9.6.3, 9.5.5. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.

How severe is CVE-2025-29923?

CVE-2025-29923 has a CVSS score of 3.7 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of github.com/redis/go-redis/v9 are affected by CVE-2025-29923?

github.com/redis/go-redis/v9 (go) versions >= 9.7.0-beta.1, < 9.7.3 is affected.

Is there a fix for CVE-2025-29923?

Yes. CVE-2025-29923 is fixed in 9.7.3, 9.6.3, 9.5.5. Upgrade to this version or later.

Is CVE-2025-29923 exploitable, and should I be worried?

Whether CVE-2025-29923 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-29923 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2025-29923?

Upgrade: github.com/redis/go-redis/v9 to 9.7.3 or later, github.com/redis/go-redis/v9 to 9.6.3 or later, github.com/redis/go-redis/v9 to 9.5.5 or later.

CVE-2025-29923 in github.com/redis/go-redis/v9

Q: How severe is CVE-2025-29923?

CVE-2025-29923 has a CVSS score of 3.7 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of github.com/redis/go-redis/v9 are affected by CVE-2025-29923?

github.com/redis/go-redis/v9 (go) versions >= 9.7.0-beta.1, < 9.7.3 is affected.

Q: Is there a fix for CVE-2025-29923?

Yes. CVE-2025-29923 is fixed in 9.7.3, 9.6.3, 9.5.5. Upgrade to this version or later.

Q: Is CVE-2025-29923 exploitable, and should I be worried?

Whether CVE-2025-29923 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-29923 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-29923?

Upgrade: github.com/redis/go-redis/v9 to 9.7.3 or later, github.com/redis/go-redis/v9 to 9.6.3 or later, github.com/redis/go-redis/v9 to 9.5.5 or later.

Summary

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

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

Impact

The issue only occurs when the CLIENT SETINFO command times out during connection establishment. The following circumstances can cause such a timeout:

The client is configured to transmit its identity. This can be disabled via the DisableIndentity flag.
There are network connectivity issues
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 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.

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2025-29923 has a CVSS score of 3.7 (Low). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (9.7.3, 9.6.3, 9.5.5); upgrading removes the vulnerable code path.

Affected versions

github.com/redis/go-redis/v9 (>= 9.7.0-beta.1, < 9.7.3) github.com/redis/go-redis/v9 (>= 9.6.0b1, < 9.6.3) github.com/redis/go-redis/v9 (>= 9.5.1, < 9.5.5)

Security releases

github.com/redis/go-redis/v9 → 9.7.3 (go) github.com/redis/go-redis/v9 → 9.6.3 (go) github.com/redis/go-redis/v9 → 9.5.5 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

We prepared a fix in https://github.com/redis/go-redis/pull/3295 and plan to release patch versions soon.

Frequently Asked Questions

What is CVE-2025-29923? CVE-2025-29923 is a low-severity improper input validation vulnerability in github.com/redis/go-redis/v9 (go), affecting versions >= 9.7.0-beta.1, < 9.7.3. It is fixed in 9.7.3, 9.6.3, 9.5.5. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
How severe is CVE-2025-29923? CVE-2025-29923 has a CVSS score of 3.7 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of github.com/redis/go-redis/v9 are affected by CVE-2025-29923? github.com/redis/go-redis/v9 (go) versions >= 9.7.0-beta.1, < 9.7.3 is affected.
Is there a fix for CVE-2025-29923? Yes. CVE-2025-29923 is fixed in 9.7.3, 9.6.3, 9.5.5. Upgrade to this version or later.
Is CVE-2025-29923 exploitable, and should I be worried? Whether CVE-2025-29923 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-29923 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-29923?
- Upgrade github.com/redis/go-redis/v9 to 9.7.3 or later
- Upgrade github.com/redis/go-redis/v9 to 9.6.3 or later
- Upgrade github.com/redis/go-redis/v9 to 9.5.5 or later