Advisory record · RUSTSEC-2026-0232

Processing of unverified relay events

CVSS 7.5 High

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.

PackageEcosystemAffectedFixed in
nostr-relay-poolcrates.io>=0.0.0-0, <0.44.30.44.3
Identifiers
RUSTSEC-2026-0232
Published
1 Aug 2026
Updated
2 Aug 2026

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

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N OSV
  • CISA KEV Not listed.
  • EPSS No score.

Timeline

  1. 31 Oct 2026, 15:18 UTC First seen by agentprime
  2. 31 Oct 2026, 15:18 UTC Confirmed by OSV

Sources

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.