Advisory

RUSTSEC-2026-0230

Also known as: None

Summary

Empty NIP-50 search filters can panic

Details

The NIP-50 event-matching path searched event content with
slice::windows(search.len()). An empty search string therefore called
slice::windows(0), which always panics instead of returning a match result.

A remote client able to submit filters to an application using this matcher could
trigger the panic with an empty NIP-50 search value. This includes clients querying an
SDK local relay. Depending on the application's panic configuration and task
isolation, the crafted filter could terminate request processing, a runtime worker, or
the entire process, causing denial of service. No confidentiality or integrity impact
is known.

Empty searches are now handled before the substring search, so the matcher returns a
defined result without constructing a zero-sized window or panicking.

Severity

High Basis: CVSS v3 score 7.5, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Dates

Published
2026-08-01 12:00 UTC
Modified
2026-08-02 18:00 UTC

Affected packages and fixes

nostr

crates.io · All systems

Affected

  • introduced 0.0.0-0, fixed 0.44.7 (semver)

Fixed versions

0.44.7

Fix

  • Fixed version 0.44.7
    cargo update -p nostr --precise 0.44.7

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences