Advisory

RUSTSEC-2026-0228

Also known as: None

Summary

NIP-04 parsing amplifies malformed ciphertext memory use

Details

The NIP-04 decryption parser split attacker-controlled content on every ?iv=
separator and collected all resulting segments before checking that the message had
the expected two parts. It also Base64-decoded the complete IV text before checking
that it represented the required 16-byte AES-CBC IV.

A malicious sender could include a large number of separators or an oversized IV in
an encrypted direct message. Applications that attempted to decrypt the message
performed avoidable allocations proportional to the malformed input, with additional
allocation amplification from the segment vector and Base64 output. This can consume
memory and CPU in clients processing messages received through a relay. It does not
weaken NIP-04 encryption or reveal plaintext or key material.

The parser now uses a single bounded split, rejects additional separators, and
validates the 24-byte encoded IV length before Base64 decoding. Malformed inputs are
returned as errors without allocating for every separator or decoding an arbitrarily
large IV.

Severity

Medium Basis: CVSS v3 score 4.3, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L

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