# Wallet event parsers accept unauthenticated events

Advisory record · `RUSTSEC-2026-0226`

- **Identifiers:** `RUSTSEC-2026-0226`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Published:** 1 Aug 2026
- **Updated:** 2 Aug 2026
- **Reviewed by a person:** No

Published by OSV at 1 Aug 2026, 12:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `nostr` (crates.io): affected `>=0.0.0-0, <0.44.7`; fixed in `0.44.7`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The nostr crate, versions before 0.44.7, has wallet event parsers for NIP-47 responses and notifications and for NIP-60 wallet events that decrypt events before checking their author. A malicious relay can deliver an event signed by an attacker, so forged wallet responses, notifications, tokens, spending records, or quotes get accepted as coming from the configured wallet. This can corrupt wallet state or make an application act on forged data. Upgrade to nostr 0.44.7 or later.

Written 8 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`, from OSV

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 15:18 UTC: First seen by agentprime
- 31 Oct 2026, 15:18 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/RUSTSEC-2026-0226)

## Sources

- [OSV: RUSTSEC-2026-0226](https://osv.dev/vulnerability/RUSTSEC-2026-0226)
- <https://crates.io/crates/nostr>
- <https://rustsec.org/advisories/RUSTSEC-2026-0226.html>
- <https://github.com/nostrdevkit/nostr/commit/2b6d6227cd884c1acb200bffa66a3f402b02a176>
- <https://github.com/nostrdevkit/nostr/commit/0b78464e39604b0f052862035f47fdabc2a536dd>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/RUSTSEC-2026-0226>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/RUSTSEC-2026-0226/>. Everything for agents: <https://agentprime.io/llms.txt>.
