CVE-2025-29923

LOWNVD 3.73.7—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 3.7 under NVD CVSS v3. EPSS exploit probability: 0.7%, top 48% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
3.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 3.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
3.7
EG Score
3.7LOWmedium confidence
EG Risk
17
EG Risk 17/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity37% × 45%
Exploitation1% × 40%
Automatability0% × 15%
EPSS PROB
0.7%
EPSS %ILE
53rd
KEV
Not listed

Published

March 20, 2025

Last Modified

September 3, 2026

References (3)

Vendor Advisories for CVE-2025-29923(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 1 ecosystem)
Go(4)
PackageVulnerable rangeFix by version rangeDependents
github.com/redis/go-redis—
  • every version on: no fix on record
—
github.com/redis/go-redis/v7—
  • every version on: no fix on record
—
github.com/redis/go-redis/v8—
  • every version on: no fix on record
—
github.com/redis/go-redis/v9—
  • 9.7.0-beta.1 up to 9.7.3: fixed in 9.7.3
  • 9.6.0b1 up to 9.6.3: fixed in 9.6.3
  • 9.5.1 up to 9.5.5: fixed in 9.5.5
  • every version up to 9.6.3: fixed in 9.6.3
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 205 total refreshes for this CVE.

  1. 2026-10-10 19:59 UTCEPSS rescore
  2. 2026-10-09 20:06 UTCEPSS rescore
  3. 2026-10-08 17:09 UTCEPSS rescore
  4. 2026-10-07 23:46 UTCEPSS rescore
  5. 2026-10-06 15:16 UTCEPSS rescore
  6. 2026-10-05 17:42 UTCEPSS rescore
  7. 2026-10-04 23:21 UTCEPSS rescore
  8. 2026-10-03 14:24 UTCEPSS rescore
  9. 2026-10-01 19:49 UTCEPSS rescore
  10. 2026-09-30 15:02 UTCEPSS rescore
  11. 2026-09-29 15:19 UTCEPSS rescore
  12. 2026-09-28 13:50 UTCEPSS rescore
  13. 2026-09-26 15:58 UTCEPSS rescore
  14. 2026-09-26 15:58 UTCEPSS rescore
  15. 2026-09-26 00:24 UTCEPSS rescore
  16. 2026-09-26 00:24 UTCEPSS rescore
  17. 2026-09-24 14:02 UTCEPSS rescore
  18. 2026-09-23 13:47 UTCEPSS rescore
  19. 2026-09-22 16:58 UTCOSV refresh
  20. 2026-09-20 20:15 UTCEPSS rescore
  21. 2026-09-18 19:27 UTCEPSS rescore
  22. 2026-09-16 14:07 UTCEPSS rescore
  23. 2026-09-16 05:13 UTCEPSS rescore
  24. 2026-09-13 16:46 UTCEPSS rescore
  25. 2026-09-12 15:00 UTCEPSS rescore
Show 75 more
  1. 2026-09-11 14:52 UTCEPSS rescore
  2. 2026-09-11 09:35 UTCEPSS rescore
  3. 2026-09-10 09:33 UTCEPSS rescore
  4. 2026-09-08 21:59 UTCEPSS rescore
  5. 2026-09-07 16:00 UTCEPSS rescore
  6. 2026-09-06 13:46 UTCEPSS rescore
  7. 2026-09-06 13:46 UTCEPSS rescore
  8. 2026-09-04 05:05 UTCEPSS rescore
  9. 2026-09-03 13:22 UTCVendor advisory
  10. 2026-09-03 03:38 UTCVendor advisory
  11. 2026-09-02 21:21 UTCEG score recompute
  12. 2026-09-02 21:21 UTCVendor advisory
  13. 2026-09-02 14:11 UTCEPSS rescore
  14. 2026-09-01 13:53 UTCEPSS rescore
  15. 2026-08-30 19:16 UTCEPSS rescore
  16. 2026-08-30 19:16 UTCEPSS rescore
  17. 2026-08-30 01:21 UTCEPSS rescore
  18. 2026-08-29 05:13 UTCOSV refresh
  19. 2026-08-28 21:40 UTCEPSS rescore
  20. 2026-08-27 14:24 UTCEPSS rescore
  21. 2026-08-26 14:45 UTCEPSS rescore
  22. 2026-08-25 13:48 UTCEPSS rescore
  23. 2026-08-24 14:16 UTCEPSS rescore
  24. 2026-08-23 00:18 UTCEPSS rescore
  25. 2026-08-21 23:48 UTCEPSS rescore
  26. 2026-08-19 17:03 UTCEPSS rescore
  27. 2026-08-18 13:47 UTCEPSS rescore
  28. 2026-08-17 13:46 UTCEPSS rescore
  29. 2026-08-16 14:55 UTCEPSS rescore
  30. 2026-08-16 02:13 UTCEPSS rescore
  31. 2026-08-15 01:29 UTCEPSS rescore
  32. 2026-08-13 21:59 UTCEPSS rescore
  33. 2026-08-12 17:01 UTCOSV refresh
  34. 2026-08-12 13:50 UTCEPSS rescore
  35. 2026-08-10 23:59 UTCEPSS rescore
  36. 2026-08-09 13:45 UTCEPSS rescore
  37. 2026-08-07 16:26 UTCEPSS rescore
  38. 2026-08-06 13:46 UTCEPSS rescore
  39. 2026-08-05 19:16 UTCEPSS rescore
  40. 2026-08-04 15:09 UTCEPSS rescore
  41. 2026-08-04 10:37 UTCEPSS rescore
  42. 2026-08-03 10:35 UTCEPSS rescore
  43. 2026-08-02 02:26 UTCEPSS rescore
  44. 2026-08-01 04:15 UTCEPSS rescore
  45. 2026-07-30 16:27 UTCEPSS rescore
  46. 2026-07-30 01:29 UTCEPSS rescore
  47. 2026-07-28 15:35 UTCEPSS rescore
  48. 2026-07-28 00:24 UTCOSV refresh
  49. 2026-07-27 14:12 UTCEPSS rescore
  50. 2026-07-26 14:53 UTCEPSS rescore
  51. 2026-07-25 14:17 UTCEPSS rescore
  52. 2026-07-24 14:17 UTCEPSS rescore
  53. 2026-07-23 02:52 UTCEG score recompute
  54. 2026-07-22 14:07 UTCEPSS rescore
  55. 2026-07-22 14:07 UTCEPSS rescore
  56. 2026-07-21 15:24 UTCEPSS rescore
  57. 2026-07-21 15:24 UTCEPSS rescore
  58. 2026-07-20 17:07 UTCEPSS rescore
  59. 2026-07-19 14:30 UTCEPSS rescore
  60. 2026-07-19 14:30 UTCEPSS rescore
  61. 2026-07-19 02:28 UTCEPSS rescore
  62. 2026-07-19 02:28 UTCEPSS rescore
  63. 2026-07-18 10:04 UTCEPSS rescore
  64. 2026-07-18 10:04 UTCEPSS rescore
  65. 2026-07-16 17:02 UTCEPSS rescore
  66. 2026-07-15 16:57 UTCEPSS rescore
  67. 2026-07-15 16:57 UTCEPSS rescore
  68. 2026-07-15 01:59 UTCEPSS rescore
  69. 2026-07-15 01:59 UTCEPSS rescore
  70. 2026-07-13 22:29 UTCEPSS rescore
  71. 2026-07-13 06:12 UTCEPSS rescore
  72. 2026-07-13 06:12 UTCEPSS rescore
  73. 2026-07-12 05:46 UTCEPSS rescore
  74. 2026-07-12 05:46 UTCEPSS rescore
  75. 2026-07-11 08:27 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-29923?
CVE-2025-29923 is a low vulnerability published on March 20, 2025. 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…
When was CVE-2025-29923 disclosed?
CVE-2025-29923 was first published on March 20, 2025, with the most recent update on September 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-29923 actively exploited?
CVE-2025-29923 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-29923?
CVE-2025-29923 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2025-29923?
A fix for CVE-2025-29923 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-29923 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-29923

Explore →

Is Your Infrastructure Affected by CVE-2025-29923?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs