CVE-2026-72568

✕ Withdrawn — historical dataHIGHPre-NVD 7.1Trending — 4 sources updated this week
7.1CVSS
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

A fix is available — apply it.

An out-of-bounds read vulnerability in Redis through 8.8.1 allows an adjacent unauthenticated attacker to cause denial of service or information disclosure by sending a specially crafted PING message to the Redis Cluster Bus port.

CVSS v3
7.1
EchelonGraph score
Not yet assessedThis CVE record was withdrawn by its numbering authority, so there is no vulnerability to rate.
EG Score
—
EG Risk
—
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 17, 2026

Advisory Details (2)

Auto-updated Aug 10, 2026
No patch confirmed yet.
generic

GitHub - redis/redis: For developers, who are building real-time data-driven applications, Redis is the preferred, fastest, and most feature-rich cache, data structure server, and document and vector query engine. · GitHub

https://github.com/redis/redis
generic

Redis - Real-time data for agents & apps

https://redis.io/

Vendor Advisories for CVE-2026-72568(3)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatvalkey-main-9.0.5-0.1.hum12026-07-22redhat

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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 28× in last 7d / 50× 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.

  1. 2026-08-20 23:55 UTCVendor advisory
  2. 2026-08-20 23:55 UTCGHSA enrichment
  3. 2026-08-18 02:04 UTCEG score recompute▼ 7.10
  4. 2026-08-18 02:04 UTCVendor advisory
  5. 2026-08-18 02:04 UTCGHSA enrichment
  6. 2026-08-17 13:52 UTCEG score recompute
  7. 2026-08-17 13:52 UTCVendor advisory
  8. 2026-08-17 13:52 UTCGHSA enrichment
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-17 04:38 UTCVendor advisory
  11. 2026-08-17 04:38 UTCGHSA enrichment
  12. 2026-08-16 16:28 UTCEG score recompute
  13. 2026-08-16 16:28 UTCVendor advisory
  14. 2026-08-16 16:28 UTCGHSA enrichment
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 04:19 UTCEG score recompute
  18. 2026-08-16 04:19 UTCVendor advisory
  19. 2026-08-16 04:19 UTCGHSA enrichment
  20. 2026-08-16 02:15 UTCEPSS rescore
  21. 2026-08-15 16:09 UTCVendor advisory
  22. 2026-08-15 16:09 UTCGHSA enrichment
  23. 2026-08-15 03:59 UTCEG score recompute
  24. 2026-08-15 03:59 UTCVendor advisory
  25. 2026-08-15 03:59 UTCGHSA enrichment
Show 25 more
  1. 2026-08-15 01:31 UTCEPSS rescore
  2. 2026-08-14 15:48 UTCVendor advisory
  3. 2026-08-14 15:48 UTCGHSA enrichment
  4. 2026-08-14 03:39 UTCEG score recompute
  5. 2026-08-14 03:39 UTCVendor advisory
  6. 2026-08-14 03:39 UTCGHSA enrichment
  7. 2026-08-13 22:00 UTCEPSS rescore
  8. 2026-08-13 15:29 UTCGHSA enrichment
  9. 2026-08-13 03:19 UTCGHSA enrichment
  10. 2026-08-12 15:09 UTCEG score recompute
  11. 2026-08-12 15:09 UTCGHSA enrichment
  12. 2026-08-12 13:51 UTCEPSS rescore
  13. 2026-08-12 02:59 UTCGHSA enrichment
  14. 2026-08-11 14:49 UTCEG score recompute
  15. 2026-08-11 14:48 UTCGHSA enrichment
  16. 2026-08-11 02:38 UTCGHSA enrichment
  17. 2026-08-10 14:29 UTCEG score recompute
  18. 2026-08-10 14:29 UTCGHSA enrichment
  19. 2026-08-10 13:36 UTCEG score recompute
  20. 2026-08-10 13:36 UTCGHSA enrichment
  21. 2026-08-10 12:23 UTCEG score recompute
  22. 2026-08-10 12:02 UTCEG score recompute
  23. 2026-08-10 11:20 UTCEG score recompute
  24. 2026-08-10 10:57 UTCEG score recompute
  25. 2026-08-10 10:56 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-72568?
CVE-2026-72568 is a high vulnerability published on August 10, 2026. An out-of-bounds read vulnerability in Redis through 8.8.1 allows an adjacent unauthenticated attacker to cause denial of service or information disclosure by sending a specially crafted PING message to the Redis Cluster Bus port.
When was CVE-2026-72568 disclosed?
CVE-2026-72568 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72568 actively exploited?
CVE-2026-72568 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 85.6% of all scored CVEs.
What is the CVSS score of CVE-2026-72568?
CVE-2026-72568 has a CVSS v4.0 base score of 7.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-72568?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72568, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-72568

Explore →

Is Your Infrastructure Affected by CVE-2026-72568?

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

Start Free Scan →Browse All CVEs