Root cause
Validation and conversion interpreted legacy serialized data differently. A separate cleanup path could free an object that another part of the program still owned. The researcher traced ownership through deserialization and failure cleanup to identify both defects. Each allocation needed to be freed exactly once; accepting an import request did not make its contents trustworthy.
Demonstrated impact
The researcher demonstrated code execution in the competition. The vendor confirms possible execution under Redis-process authority for an authenticated user with import permission. Host or tenant reach depends on deployment privileges and isolation; it is not established for every Redis installation.
What to check for
- Make ownership transfer and cleanup responsibility explicit on success and failure paths.
- Require validators and converters to interpret the same serialized representation consistently.
- Follow vendor patch guidance; restrict unnecessary import permissions using access controls while remediation is assessed.
Award and evidence
How the award was verified, and what the record does not establish
One individually identified competition entry. The organizer uses $; its current rules establish US-dollar notation but concern 2026, not an archived 2025 rules snapshot. Exact award decision and cash settlement are unknown.
- The vendor advisory also credits Joseph Surin; the reviewed award names Emil Lerner only, so no reward allocation to the additional credited researcher is inferred.
- The advisory’s patched-version field still says TBD, while the official 8.6.3 release explicitly lists the CVE as fixed; the CNA affected range also excludes 8.6.3.
- The researcher explains double-free mechanisms, while the CNA supplies CWE-122; neither classification is silently substituted for the other.
- Original vendor-report, award decision and settlement dates remain unknown; June 2 publication year is inferred.
- Current rules provide explicit USD context but are not the archived 2025 rules.
Timeline
- Published
- 2026-06-02inferred · The article displays June 2; 2026 is inferred from its completed May 5, 2026 remediation timeline.
- Public Disclosure
- 2025-12-10explicit · Public competition demonstration; separate from later vendor advisory and technical publication.
- Fixed
- 2026-05-05explicit · Official Redis 8.6.3 release names the CVE. Researcher also identifies fixed versions in four other maintained series.
- Award Announced
- 2025-12-16explicit · Organizer recap confirms the per-entry award; decision and payment dates remain unknown.
Related cases
- Redis replication state changes invalidated an active interpreter
Redis · Memory safety and parser contracts · USD 30,000
- PostgreSQL cryptographic parsing omitted a buffer-capacity check
PostgreSQL · Memory safety and parser contracts · USD 30,000
- PostgreSQL text-encoding invariant failure caused memory corruption
PostgreSQL · Memory safety and parser contracts · USD 30,000
- MariaDB JSON normalization exceeded allocated buffer capacity
MariaDB · Memory safety and parser contracts · USD 30,000
Sources
- ZeroDay.cloud 2025 individual competition resultsNir Ohfeld / Wiz Research · reviewed 2026-10-02
- ZeroDay.cloud vulnerability trackerWiz / ZeroDay.cloud · reviewed 2026-10-02
- ZeroDay.cloud current rules: US-dollar denominationWiz · reviewed 2026-10-02
- CVE-2026-25243: Two Redis RESTORE Bugs Leading to RCEEmil Lerner / ZeroDay.cloud · reviewed 2026-10-02
- Redis serialized-value validation advisory GHSA-c8h9-259x-jff4Redis · reviewed 2026-10-02
- CVE-2026-25243 CNA recordRedis / GitHub CNA · reviewed 2026-10-02
- Redis 8.6.3 security releaseRedis · reviewed 2026-10-02
Record reviewed 2026-10-02. Snapshot af2809c308fc. Open the complete JSON contract.