CVE-2026-66373

{"id": "CVE-2026-66373", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-66373", "role": "CISA Coordinator", "options": [{"exploitation": "poc"}, {"automatable": "no"}, {"technicalImpact": "total"}], "version": "2.0.3", "timestamp": "2026-07-27T00:00:00+00:00"}}], "cvssMetricV31": [{"type": "Secondary", "source": "cve@mitre.org", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.5, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "HIGH", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 1.6}]}, "affected": [{"source": "cve@mitre.org", "affectedData": [{"vendor": "Redis", "product": "Redis", "versions": [{"status": "affected", "version": "0", "lessThan": "8.8.0", "versionType": "semver"}], "defaultStatus": "unaffected"}]}], "published": "2026-07-25T01:16:26.277", "references": [{"url": "https://github.com/berabuddies/redis-poc", "source": "cve@mitre.org"}, {"url": "https://github.com/redis/redis/compare/8.6.4...8.8.0", "source": "cve@mitre.org"}, {"url": "https://github.com/redis/redis/pull/15081", "source": "cve@mitre.org"}, {"url": "https://news.ycombinator.com/item?id=49024938", "source": "cve@mitre.org"}, {"url": "https://x.com/Fried_rice/status/2080059356322918777", "source": "cve@mitre.org"}, {"url": "https://github.com/berabuddies/redis-poc", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Received", "weaknesses": [{"type": "Secondary", "source": "cve@mitre.org", "description": [{"lang": "en", "value": "CWE-415"}]}], "descriptions": [{"lang": "en", "value": "Redis before 8.8.0, in the unusual case where an authenticated attacker can execute RESTORE, allows remote code execution via a RESTORE payload where the same NACK (pending entry) is referenced by more than one consumer, because deleting both consumers via XGROUP DELCONSUMER leads to a double free. NOTE: this issue exists because of an incomplete fix for CVE-2026-25243."}], "lastModified": "2026-07-28T05:17:17.507", "sourceIdentifier": "cve@mitre.org"}