Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ RUSTSEC-2026-0232 — nostr-relay-pool

⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Processing of unverified relay events

The processed events received from a relay through admission-policy and database

paths before verifying that the serialized fields matched the claimed event ID and

signature. In particular, a database result for the claimed ID could cause

verification to be skipped. The verification cache also keyed successful checks by a

64-bit hash instead of the complete event ID.

A malicious relay could send an event whose claimed ID referred to a known database

entry while its content, tags, author, or signature differed from that ID. The forged

event could then reach policy callbacks or other SDK processing as if it were

authentic. A cache-key collision provided a second path for an unverified event to be

treated as previously verified. This undermines event integrity but does not reveal

private keys or enable the attacker to produce a valid signature for the altered

event.

The SDK now verifies each event before policy evaluation, database lookup, or

propagation decisions, and the verification cache stores the complete EventId so a

truncated hash collision cannot stand in for successful verification.

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity high, availability none.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

  • Attack vector: Network — reachable from anywhere that can route to the service.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: None — an unauthenticated stranger can try it.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: None.
  • Integrity impact: High — total loss, or loss the attacker controls.
  • Availability impact: None.

Affected software

RUSTSEC-2026-0232 is recorded against 1 package.

  • nostr-relay-pool

Timeline and source

Published on 1 August 2026 and last revised on 2 August 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

crates.io (Package)
rustsec.org (Advisory)
github.com (Web)

Other advisories for this package

nostr-relay-pool has other advisories on record. If you are patching this one, these are worth checking on the same host:

Details

Severity Unknown
CVSS Score N/A
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2026-08-01
Updated 2026-08-20
Modified 2026-08-02
Fix URL N/A

Affected Packages

Software From version Fixed in
nostr-relay-pool — —

Similar Threats

Free Vulnerability Check

Is your site affected by RUSTSEC-2026-0232?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against RUSTSEC-2026-0232 and other known CVE records.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesRustsecRustsec 2026
✓