Advisory

RUSTSEC-2026-0226

Also known as: None

Summary

Wallet event parsers accept unauthenticated events

Details

The NIP-47 response and notification parsers and the NIP-60 wallet event parsers
decrypted relay-provided events before verifying their kind, computed event ID,
signature, and expected wallet public key. The decryption peer was derived from the
untrusted event author, so successful decryption did not prove that the configured
wallet created the event.

An attacker can sign an event with their own key and derive the corresponding shared
secret with the victim's public key. A malicious relay delivering that event could
therefore cause attacker-chosen encrypted content to be parsed as a response,
notification, token, spending record, or quote from the configured wallet. This can
corrupt wallet state or cause an application to act on forged wallet data. The issue
does not expose the victim's private key or decrypt events authored by the legitimate
wallet.

The affected parsers now verify the event kind, ID, signature, and exact configured
wallet author before attempting decryption or parsing the plaintext.

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:H/A:N

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