Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
RUSTSEC-2026-0224
No affected components available
The nostr-relay-pool crate cached the result of event signature verification
before the check was actually performed. Because the entry was inserted
unconditionally, a first delivery whose signature failed was still recorded
in the cache. A subsequent delivery of the same event (identical ID,
but with a forged signature) would then hit the cache, causing signature
verification to be skipped entirely. The forged event was passed on to
NostrDatabase::save_event() as if it had been validated.
Applications that connect to untrusted or compromised Nostr relays and persist received events are vulnerable. An attacker can inject arbitrary events without a valid signature into the application's trusted database, enabling impersonation of any public key or corruption of application state derived from stored events.
The issue does not compromise confidentiality or availability. It solely undermines the integrity of stored event data.
The fix, released in version 0.44.2, moves the cache insertion to occur only after a successful signature verification, so that failed attempts never create a cache entry.
Credit
Discovered and reported by Ali Al-Sorehi
The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker does not need any special privileges or access rights. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a high impact on the integrity of the data.
Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.
Probability that this vulnerability will be exploited in the wild within the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard