Intel

AIKIDO-2026-588861

nostr-sdk is vulnerable to Uncontrolled Resource Consumption

GHSA-9p75-m8cr-4h25Published Aug 5, 2026
August 5, 2026

75

CVE Score

High

Uncontrolled Resource Consumption

Are you affected? Scan for Free

TL;DR

The NIP-44 decryption entry point Base64-decodes the complete payload before checking its version or enforcing a size limit, and for v2 payloads authenticates the decoded buffer with HMAC even when it far exceeds the maximum supported payload. A malicious relay or event author can deliver an oversized value that forces allocation and Base64 and HMAC work proportional to its size before authentication fails, without knowledge of the conversation key. Repeated payloads can exhaust memory or CPU and make the receiving application unavailable. The fix reads the version prefix first, bounds the payload to the largest value the current v2 encoder can emit, and rejects oversized encoded and decoded payloads before full allocation or HMAC processing.

How do I fix this?

Upgrade the org.rust-nostr:nostr-sdk, org.rust-nostr:nostr-sdk-jvm, or org.rust-nostr:nostr-sdk-kmp library to the patch version.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range and your application decrypts NIP-44 content received from relays or event authors.

Package

Versions

0.0.1 - 0.44.7

Fixed in 0.44.8

Background info

nostr-sdk is vulnerable to Uncontrolled Resource Consumption in versions 0.0.1 - 0.44.7.

Get secure today,
quickly and for free.

Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.

No credit card required | Scan results in 32 seconds.

Trusted by 150k+ orgs
  • Revolut
  • n8n
  • Lovable
  • Deel
  • Prove
  • Omnea