Email me

Rust advisories / nostr

Vulnerability HighRUSTSEC-2026-0227 · nostr

RUSTSEC-2026-0227: NIP-44 v2 decryption permits resource exhaustion

Short answerA security vulnerability in the nostr crate: NIP-44 v2 decryption permits resource exhaustion. High severity (CVSS 7.5). Fixed in 0.44.7: update to a fixed version.

Cratenostr
TypeVulnerability (denial-of-service)
Affected versionsBefore 0.44.7.
Fixed in0.44.7
SeverityHigh, CVSS 7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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-44 decryption entry point Base64-decoded the complete attacker-controlled payload before determining its version or enforcing any size limit. For v2 payloads, the decoded buffer was then authenticated with HMAC even when it was much larger than the maximum payload supported by the crate's current v2 codec.

A malicious relay or event author could deliver an oversized value to an application that decrypts NIP-44 content. The value caused memory allocation and Base64 and HMAC work proportional to its size before authentication failed; knowledge of the conversation key was not required to consume those initial resources. Repeated payloads could exhaust memory or CPU and make the receiving application unavailable. The issue does not disclose plaintext or key material and does not bypass message authentication.

Decryption now reads only the encoded version prefix first, derives the bound from the largest payload the current v2 encoder can emit, and rejects oversized encoded and decoded payloads before full allocation or HMAC processing. The limit remains in the v2 implementation so a future codec with a different length format can define its own bound.

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