# RUSTSEC-2026-0226: Wallet event parsers accept unauthenticated events

> Attackers can forge wallet events via malicious relays, causing applications to process fake data and corrupt wallet state.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Aug 2026

## What is RUSTSEC-2026-0226?

RUSTSEC-2026-0226 is a missing authorization vulnerability in nostr, published on 1 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The NIP-47 response and notification parsers and the NIP-60 wallet event parsers
decrypted relay-provided events before verifying their kind, computed event ID,
signature, and expected wallet public key. The decryption peer was derived from the
untrusted event author, so successful decryption did not prove that the configured
wallet created the event.

An attacker can sign an event with their own key and derive the corresponding shared
secret with the victim's public key. A malicious relay delivering that event could
therefore cause attacker-chosen encrypted content to be parsed as a response,
notification, token, spending record, or quote from the configured wallet. This can
corrupt wallet state or cause an application to act on forged wallet data. The issue
does not expose the victim's private key or decrypt events authored by the legitimate
wallet.

The affected parsers now verify the event kind, ID, signature, and exact configured
wallet author before attempting decryption or parsing the plaintext.

## Which versions are affected by RUSTSEC-2026-0226?

1 open source package ship an affected version, including nostr.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nostr` | crates.io | From 0.0.0-0 | 0.44.7 |

## How do I fix RUSTSEC-2026-0226?

Upgrade nostr to 0.44.7 or later.

## Is RUSTSEC-2026-0226 being exploited?

There is no known exploitation of RUSTSEC-2026-0226 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2026-0226 and fix it if it is affected.

What it is: RUSTSEC-2026-0226 is a missing authorization vulnerability in nostr, published on 1 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of RUSTSEC-2026-0226 in the wild and no public exploit code.

Affected packages and fixed versions:
- nostr (crates.io): affected from 0.0.0-0; fixed in 0.44.7

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/RUSTSEC-2026-0226/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0226/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2026-0226

---
From sbomify Insights: https://insights.sbomify.com/RUSTSEC-2026-0226/
Summaries are generated and may contain mistakes; the official description above is the record.