Advisory record · GHSA-f96q-5f6p-v7cj

Verification cache poisoning allows forged Nostr events to bypass signature validation

CVSS 7.5 High

Published by the GitHub Advisory Database 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.20.44.2
Identifiers
GHSA-f96q-5f6p-v7cj · RUSTSEC-2026-0224
Published
1 Aug 2026
Updated
1 Aug 2026

Machine-written summary

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

The nostr-relay-pool crate, versions before 0.44.2, cached signature verification results before the check ran, so a forged event with the same ID as a previously rejected event could skip verification. An attacker controlling or compromising a relay that an application connects to can inject events without valid signatures into that application's stored data, enabling impersonation of public keys. Upgrade to nostr-relay-pool 0.44.2 or later.

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.