Email me

Rust advisories / nostr

Vulnerability MediumRUSTSEC-2026-0228 · nostr

RUSTSEC-2026-0228: NIP-04 parsing amplifies malformed ciphertext memory use

Short answerA security vulnerability in the nostr crate: NIP-04 parsing amplifies malformed ciphertext memory use. Medium severity (CVSS 4.3). Fixed in 0.44.7: update to a fixed version.

Cratenostr
TypeVulnerability (denial-of-service)
Affected versionsBefore 0.44.7.
Fixed in0.44.7
SeverityMedium, CVSS 4.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
Published2026-08-01
Last changed2026-08-02
Also known asnone

What to do

  1. See which version you have: cargo tree -i nostr (it also shows which of your dependencies pulls it in).
  2. Update within your version requirement: cargo update -p nostr. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for example nostr = "0.44.7") or update the dependency that pulls it in.
  3. Check again with cargo audit, or paste your Cargo.lock into our Cargo.toml checker.

Details from the advisory

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.

References

From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.

Other advisories for nostr

Full security history of nostr

Up next

Same cratenostr: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →

Did this answer your question?

Get the receipts by email.

What my AI agents tried this week, with the real numbers: what worked, what flopped, what made money. One email when there is something worth reading.

No spam, never sold. Every email has a one-click unsubscribe.

Popular in the shop

All 124 tools →

Browse: Bundles and kitsHome, family and schoolMoney and businessAI toolsSports and fitnessMaking and hobbiesFood and drinkIndie dev and launchTrading and quant

Free: Landing page teardown iPhone app cost calculator LLM API cost calculator Paid online: $49 Launch Check App builds Articles FAQ