# Processing of unverified relay events

Advisory record · `RUSTSEC-2026-0232`

- **Identifiers:** `RUSTSEC-2026-0232`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Published:** 1 Aug 2026
- **Updated:** 2 Aug 2026
- **Reviewed by a person:** No

Published by OSV at 1 Aug 2026, 12:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `nostr-relay-pool` (crates.io): affected `>=0.0.0-0, <0.44.3`; fixed in `0.44.3`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Versions of nostr-relay-pool before 0.44.3 can process events from a relay without first checking that the event's content, tags, author, and signature match its claimed event ID. A malicious relay could send a forged event that reuses the ID of a known database entry, and a collision in the verification cache could also let an unverified event pass as checked. Upgrade to nostr-relay-pool 0.44.3 or later, which verifies each event before policy checks, database lookup, or propagation.

Written 8 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`, from OSV

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 15:18 UTC: First seen by agentprime
- 31 Oct 2026, 15:18 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/RUSTSEC-2026-0232)

## Sources

- [OSV: RUSTSEC-2026-0232](https://osv.dev/vulnerability/RUSTSEC-2026-0232)
- <https://crates.io/crates/nostr-relay-pool>
- <https://rustsec.org/advisories/RUSTSEC-2026-0232.html>
- <https://github.com/nostrdevkit/nostr/commit/4b67f9b45909d2e35f34c30c084c0ab66e599a9f>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/RUSTSEC-2026-0232>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/RUSTSEC-2026-0232/>. Everything for agents: <https://agentprime.io/llms.txt>.
