fix(deps): update module github.com/redis/go-redis/v9 to v9.7.3 [security] (main)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
github.com/redis/go-redis/v9	v9.7.0 -> v9.7.3

GitHub Vulnerability Alerts

CVE-2025-29923

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

Patches

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

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

---

Release Notes

redis/go-redis (github.com/redis/go-redis/v9)

v9.7.3

Compare Source

What's Changed

• fix: handle network error on SETINFO (#​3295) (CVE-2025-29923)

Full Changelog: redis/go-redis@v9.7.1...v9.7.3

v9.7.2

Compare Source

v9.7.1

Compare Source

Changes

• Recognize byte slice for key argument in cluster client hash slot computation (#​3049)
• fix(search&aggregate):fix error overwrite and typo #​3220 (#​3224)
• fix: linter configuration (#​3279)
• fix(search): if ft.aggregate use limit when limitoffset is zero (#​3275)
• Reinstate read-only lock on hooks access in dialHook to fix data race (#​3225)
• fix: flaky ClientKillByFilter test (#​3268)
• chore: fix some comments (#​3226)
• fix(aggregate, search): ft.aggregate bugfixes (#​3263)
• fix: add unstableresp3 to cluster client (#​3266)
• Fix race condition in clusterNodes.Addrs() (#​3219)
• SortByWithCount FTSearchOptions fix (#​3201)
• Eliminate redundant dial mutex causing unbounded connection queue contention (#​3088)
• Add guidance on unstable RESP3 support for RediSearch commands to README (#​3177)

🚀 New Features

• Add guidance on unstable RESP3 support for RediSearch commands to README (#​3177)

🐛 Bug Fixes

• fix(search): if ft.aggregate use limit when limitoffset is zero (#​3275)
• fix: add unstableresp3 to cluster client (#​3266)
• fix(aggregate, search): ft.aggregate bugfixes (#​3263)
• SortByWithCount FTSearchOptions fix (#​3201)
• Recognize byte slice for key argument in cluster client hash slot computation (#​3049)

Contributors

We'd like to thank all the contributors who worked on this release!

@​ofekshenawa, @​Cgol9, @​LINKIWI, @​shawnwgit, @​zhuhaicity, @​bitsark, @​vladvildanov, @​ndyakov

Full Changelog: redis/go-redis@v9.7.0...v9.7.1

---

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.