{"answers":{"affected":"1 open source package ship an affected version, including nostr.","exploited":"There is no known exploitation of RUSTSEC-2026-0226 in the wild and no public exploit code.","fix":"Upgrade nostr to 0.44.7 or later.","what":"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."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0226 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of RUSTSEC-2026-0226 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nostr (crates.io): affected from 0.0.0-0; fixed in 0.44.7\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/RUSTSEC-2026-0226/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0226/index.md)","id":"RUSTSEC-2026-0226","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0226/index.md","name":"RUSTSEC-2026-0226","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust wallet library","requires_auth":"none","summary":"Attackers can forge wallet events via malicious relays, causing applications to process fake data and corrupt wallet state.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"The NIP-47 response and notification parsers and the NIP-60 wallet event parsers\ndecrypted relay-provided events before verifying their kind, computed event ID,\nsignature, and expected wallet public key. The decryption peer was derived from the\nuntrusted event author, so successful decryption did not prove that the configured\nwallet created the event.\n\nAn attacker can sign an event with their own key and derive the corresponding shared\nsecret with the victim's public key. A malicious relay delivering that event could\ntherefore cause attacker-chosen encrypted content to be parsed as a response,\nnotification, token, spending record, or quote from the configured wallet. This can\ncorrupt wallet state or cause an application to act on forged wallet data. The issue\ndoes not expose the victim's private key or decrypt events authored by the legitimate\nwallet.\n\nThe affected parsers now verify the event kind, ID, signature, and exact configured\nwallet author before attempting decryption or parsing the plaintext.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Wallet event parsers accept unauthenticated events","id":"RUSTSEC-2026-0226","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.44.7"],"introduced":["0.0.0-0"],"last_affected":[],"package":"nostr","purl":"pkg:cargo/nostr","source":"RUSTSEC-2026-0226"}],"products":null,"published":"2026-08-01","related":[],"sources":[{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can forge wallet events via malicious relays, causing applications to process fake data and corrupt wallet state.","url":"https://insights.sbomify.com/RUSTSEC-2026-0226/"}