CVE-2026-92925

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

Score 7.1 from GitHub Security Advisory published 2026-09-17. A secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in Redis community. The cluster bus packet parser, responsible for handling PING, PONG, and MEET packets, fails to properly validate string-carrying extensions for null-termination. This oversight allows a remote attacker to craft a malicious packet, leading to an out-of-bounds read when the packet's payload is processed. Successful exploitation of this vulnerability could result in the disclosure of sensitive information or a remote denial of service (DoS).

CVSS v3
7.1
EG Score
7.1HIGHhigh confidence
EG Risk
32
EG Risk 32/100CISA SSVC

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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 17, 2026

Last Modified

September 22, 2026

Advisory Details (3)

Auto-updated Sep 17, 2026
Patch available. Sources: github_commit, github_pr, github_release.
github_release Patch Available

8.10.0

Patch available: redis/redis 8.10.0

https://github.com/redis/redis/releases/tag/8.10.0
github_pr Patch Available

Reject cluster bus PING extensions with missing null terminator

Patch available: redis/redis 8.10-rc1 (PR #15263 merged 2026-06-05)

https://github.com/redis/redis/pull/15263
github_commit Patch Available

commit 37894faeea11 (redis/redis)

Patch available: redis/redis 8.10-rc1 (contains commit 37894faeea11)

https://github.com/redis/redis/commit/37894faeea11e2db28b9fc2af378a762d2c36523

Vendor Advisories for CVE-2026-92925(4)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatredis:7-9040020260917140622.92026-09-21redhat
redhatredis:7-9060020260917140656.92026-09-21redhat
redhatredis:7-9080020260821173335.92026-09-08redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
redis5:7.0.11-1 ... 5:7.0.15-1~deb12u9 (17 versions)
  • every version up to 5:7.0.15-1~deb12u10: fixed in 5:7.0.15-1~deb12u10
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
redis5:8.0.2-3 ... 5:8.6.3-1 (12 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
redis5:8.0.2-3, 5:8.0.4-1, 5:8.0.5-1, 5:8.0.6-1, 5:8.0.6-2
  • every version up to 5:8.0.6-3: fixed in 5:8.0.6-3
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 37× in last 7d / 130× 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 130 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-92925?
CVE-2026-92925 is a high vulnerability published on September 17, 2026. A flaw was found in Redis community. The cluster bus packet parser, responsible for handling PING, PONG, and MEET packets, fails to properly validate string-carrying extensions for null-termination. This oversight allows a remote attacker to craft a malicious packet, leading to an out-of-bounds…
When was CVE-2026-92925 disclosed?
CVE-2026-92925 was first published on September 17, 2026, with the most recent update on September 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92925 actively exploited?
CVE-2026-92925 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-92925?
CVE-2026-92925 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-92925?
A fix for CVE-2026-92925 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-92925 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-2026-92925

Explore →

Is Your Infrastructure Affected by CVE-2026-92925?

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

Book a Demo →Browse All CVEs