AI Science Tracker

Retried Redis creation writes can restore consumed one-time records

Yopass · AI involvement attributed to Anthropic's OSS Scanner

Finding and attribution

On Redis, a delayed creation SET may arrive after a retry succeeds and its returned one-time link has already been consumed, restoring the record and its full lifetime. Requires a Redis network interruption and ordering where consumption/state change precedes the delayed write; an ordinary HTTP client cannot trigger it. Redis alone is affected, and another read still requires the full link and applicable authentication.

Product: Yopass. AI system: Anthropic's OSS Scanner. Team / organization: Anthropic.

CVE identifiers: Not established in the cited evidence.

AI and human contribution (source account): The Yopass maintainer's case-specific security advisory explicitly credits Anthropic's OSS Scanner as discoverer (tracking identifier ANT-2026-MXD9LKP9). It does not name a model version or internal discovery date.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: The public maintainer advisory documents the finding; it does not establish whether defenders knew of it or whether it was exploited before disclosure.

Remediation status: fix documented. Yopass 16.0.0 fixes the issue (commit 651006f0105b319cdf6ba44c26579ccdf6c81cb7). Affected-version scope: Versions 14.2.0 through 15.1.0; fixed in 16.0.0 by executing Redis Put SET inside MULTI/EXEC with TxPipelined. An ambiguous failed operation may still have committed server-side. Patch availability does not establish downstream deployment.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 17 Oct 2026. AI attribution dated 17 Oct 2026. Sources checked 16 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: Not available · no assessment established here. Documented technical effects: other.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

No source-backed CVSS assessment is established in this catalog.

Case-level evidence: other.
Prerequisites / affected scope: A Redis retry race can restore a consumed record, violating one-time deletion semantics. The advisory does not claim plaintext access or authentication bypass..
Exploitation evidence: The advisory describes a possible or reproducible trigger as stated; it does not report observed exploitation in the wild.. Impact source · checked 16 Nov 2026.

Documented fix: Yopass 16.0.0 fixes the issue (commit 651006f0105b319cdf6ba44c26579ccdf6c81cb7). Affected-version scope: Versions 14.2.0 through 15.1.0; fixed in 16.0.0 by executing Redis Put SET inside MULTI/EXEC with TxPipelined. An ambiguous failed operation may still have committed server-side. Patch availability does not establish downstream deployment.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases