Rust advisories / nostr-relay-pool
UnmaintainedRUSTSEC-2026-0243 · nostr-relay-pool
RUSTSEC-2026-0243: `nostr-relay-pool` is unmaintained
Short answerNot a bug report: nostr-relay-pool is no longer maintained, so future security issues will not be fixed. Plan to move to a maintained alternative.
| Crate | nostr-relay-pool |
|---|---|
| Type | Unmaintained |
| Affected versions | Every version. |
| Fixed in | not applicable (the crate is unmaintained) |
| Severity | not scored |
| Published | 2026-08-03 |
| Last changed | 2026-08-09 |
| Also known as | none |
What to do
- Look for a maintained fork or alternative crate.
- If you cannot move yet, acknowledge it in your audit config so CI stays green while you plan: add
"RUSTSEC-2026-0243"toignorein.cargo/audit.tomlordeny.toml, with a comment saying why. - Find who pulls it in:
cargo tree -i nostr-relay-pool.
Details from the advisory
The nostr-relay-pool crate is no longer actively maintained as a standalone crate.
Its functionality has been incorporated into nostr-sdk starting with version 0.45.0.
Users should migrate to nostr-sdk.
References
- Package: crates.io/crates/nostr-relay-pool
- Advisory: rustsec.org/advisories/RUSTSEC-2026-0243.html
- Report: github.com/nostrdevkit/nostr/issues/1415
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Other advisories for nostr-relay-pool
- Vulnerability HighRUSTSEC-2026-0224 · 2026-08-01Verification cache poisoning allows forged Nostr events to bypass signature validation
- Vulnerability HighRUSTSEC-2026-0231 · 2026-08-01Relay authentication challenges can exhaust memory
- Vulnerability HighRUSTSEC-2026-0232 · 2026-08-01Processing of unverified relay events
Up next
Same cratenostr-relay-pool: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?