Advisory

RUSTSEC-2026-0227

Also known as: None

Summary

NIP-44 v2 decryption permits resource exhaustion

Details

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.

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