AIKIDO-2026-877284

TL;DR

The relay pool passes events received from a relay through admission-policy and database paths before confirming that the serialized fields match the claimed event id and signature, and a database result for the claimed id can cause verification to be skipped. The verification cache also keys successful checks by a 64-bit hash rather than the full event id. A malicious relay can send an event whose claimed id matches a known database entry while its content, tags, author, or signature differ, so a forged event reaches policy callbacks or other processing as authentic, with a cache-key collision offering a second bypass path. The fix verifies each event before policy evaluation, database lookup, or propagation and stores the complete event id in the verification cache.