# RUSTSEC-2026-0243: `nostr-relay-pool` is unmaintained

> The nostr-relay-pool crate is unmaintained, requiring users to migrate to nostr-sdk to ensure continued security support.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 3 Aug 2026

## What is RUSTSEC-2026-0243?

RUSTSEC-2026-0243 is a vulnerability in nostr-relay-pool, published on 3 Aug 2026. 

### Official description

The `nostr-relay-pool` crate is no longer actively maintained as a standalone crate.

Its functionality has been incorporated into [`nostr-sdk`](https://crates.io/crates/nostr-sdk) starting with version `0.45.0`.

Users should migrate to [`nostr-sdk`](https://crates.io/crates/nostr-sdk).

## Which versions are affected by RUSTSEC-2026-0243?

1 open source package ship an affected version, including nostr-relay-pool.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nostr-relay-pool` | crates.io | From 0.0.0-0 | None |

## How do I fix RUSTSEC-2026-0243?

No fix has been published for RUSTSEC-2026-0243 yet. Limit exposure of the affected software until one is available.

## Is RUSTSEC-2026-0243 being exploited?

There is no known exploitation of RUSTSEC-2026-0243 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2026-0243 and fix it if it is affected.

What it is: RUSTSEC-2026-0243 is a vulnerability in nostr-relay-pool, published on 3 Aug 2026. 
Exploitation: There is no known exploitation of RUSTSEC-2026-0243 in the wild and no public exploit code.

Affected packages and fixed versions:
- nostr-relay-pool (crates.io): affected from 0.0.0-0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/RUSTSEC-2026-0243/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0243/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2026-0243

---
From sbomify Insights: https://insights.sbomify.com/RUSTSEC-2026-0243/
Summaries are generated and may contain mistakes; the official description above is the record.