Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ RUSTSEC-2026-0224 — nostr-relay-pool

⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Verification cache poisoning allows forged Nostr events to bypass signature validation

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](https://github.com/aykoooo)

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity high, availability none.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

  • Attack vector: Network — reachable from anywhere that can route to the service.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: None — an unauthenticated stranger can try it.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: None.
  • Integrity impact: High — total loss, or loss the attacker controls.
  • Availability impact: None.

Affected software

RUSTSEC-2026-0224 is recorded against 1 package.

  • nostr-relay-pool

Timeline and source

Published on 1 August 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

crates.io (Package)
rustsec.org (Advisory)
github.com (Web)

Other advisories for this package

nostr-relay-pool has other advisories on record. If you are patching this one, these are worth checking on the same host:

Details

Severity Unknown
CVSS Score N/A
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2026-08-01
Updated 2026-08-20
Modified 2026-08-01
Fix URL N/A

Affected Packages

Software From version Fixed in
nostr-relay-pool — —

Similar Threats

Free Vulnerability Check

Is your site affected by RUSTSEC-2026-0224?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against RUSTSEC-2026-0224 and other known CVE records.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesRustsecRustsec 2026
✓