# RUSTSEC-2026-0232: Processing of unverified relay events

> A malicious relay can bypass event verification, allowing forged events to be processed as authentic, compromising data integrity in the SDK.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Aug 2026

## What is RUSTSEC-2026-0232?

RUSTSEC-2026-0232 is a vulnerability in nostr-relay-pool, published on 1 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

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

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 | 0.44.3 |

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

Upgrade nostr-relay-pool to 0.44.3 or later.

## Is RUSTSEC-2026-0232 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: RUSTSEC-2026-0232 is a vulnerability in nostr-relay-pool, published on 1 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of RUSTSEC-2026-0232 in the wild and no public exploit code.

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

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-0232/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0232/index.md)
```

## Sources

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

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